{"api_version":"1","generated_at":"2026-09-02T03:59:40+00:00","cve":"CVE-2026-81928","urls":{"html":"https://cve.report/CVE-2026-81928","api":"https://cve.report/api/cve/CVE-2026-81928.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-81928","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-81928"},"summary":{"title":"Net::DNS versions before 1.57 for Perl allow memory exhaustion via unbounded recursion in sig_data when re-encoding a message with a misplaced TSIG record","description":"Net::DNS versions before 1.57 for Perl allow memory exhaustion via unbounded recursion in sig_data when re-encoding a message with a misplaced TSIG record.\n\nsig_data signs a message by re-encoding it, and removes TSIG records only from the additional section. A TSIG decoded into the answer or authority section survives that step and is signed again, so encoding re-enters sig_data with no termination condition. Decoding does not reject such a message: a TSIG that is not the last record on the wire raises \"misplaced or corrupt TSIG\", but the error is caught, reported as a warning, and the record is left in the packet. RFC 8945 section 5.2 requires the message to be dropped.\n\nThe recursion is reached only when the decoded TSIG carries an empty MAC, since a MAC recovered from the wire short-circuits the signing step. It is reached only from code that re-encodes a message it decoded, such as a forwarder or a proxy. A decoded message that is never re-encoded is unaffected. Message direction does not matter: a query reaches the same path as a response.\n\nEach cycle re-encodes the whole message, so fewer than 100 bytes on the wire exhaust available memory and terminate the process.","state":"PUBLISHED","assigner":"CPANSec","published_at":"2026-09-02 00:18:26","updated_at":"2026-09-02 00:18:26"},"problem_types":["CWE-674","CWE-674 CWE-674 Uncontrolled Recursion"],"metrics":[],"references":[{"url":"https://metacpan.org/release/NLNETLABS/Net-DNS-1.56/source/lib/Net/DNS/RR/TSIG.pm#L245-262","name":"https://metacpan.org/release/NLNETLABS/Net-DNS-1.56/source/lib/Net/DNS/RR/TSIG.pm#L245-262","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://rt.cpan.org/Ticket/Display.html?id=181125","name":"https://rt.cpan.org/Ticket/Display.html?id=181125","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://metacpan.org/release/NLNETLABS/Net-DNS-1.56/source/lib/Net/DNS/RR/TSIG.pm#L62-73","name":"https://metacpan.org/release/NLNETLABS/Net-DNS-1.56/source/lib/Net/DNS/RR/TSIG.pm#L62-73","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://metacpan.org/release/NLNETLABS/Net-DNS-1.57/changes","name":"https://metacpan.org/release/NLNETLABS/Net-DNS-1.57/changes","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://datatracker.ietf.org/doc/html/rfc8945#section-5.2","name":"https://datatracker.ietf.org/doc/html/rfc8945#section-5.2","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-81928","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-81928","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade to Net-DNS 1.57 or later.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"For deployments that are not able to upgrade to Net-DNS 1.57, reject a decoded message before re-encoding it if a TSIG record appears anywhere but the final position of the additional section.","time":"","lang":"en"}],"exploits":[],"credits":[{"source":"CNA","value":"Naseeb Dangi and Xiang Li from AOSP Lab @ Nankai University","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"collectionURL":"https://cpan.org/modules","defaultStatus":"unaffected","modules":["Net::DNS"],"packageName":"Net-DNS","packageURL":"pkg:cpan/Net-DNS","programFiles":["lib/Net/DNS/RR/TSIG.pm"],"programRoutines":[{"name":"Net::DNS::RR::TSIG::sig_data"}],"repo":"https://www.net-dns.org/svn/net-dns/","versions":[{"lessThan":"1.57","status":"affected","version":"0","versionType":"custom"}]}],"credits":[{"lang":"en","type":"reporter","value":"Naseeb Dangi and Xiang Li from AOSP Lab @ Nankai University"}],"descriptions":[{"lang":"en","value":"Net::DNS versions before 1.57 for Perl allow memory exhaustion via unbounded recursion in sig_data when re-encoding a message with a misplaced TSIG record.\n\nsig_data signs a message by re-encoding it, and removes TSIG records only from the additional section. A TSIG decoded into the answer or authority section survives that step and is signed again, so encoding re-enters sig_data with no termination condition. Decoding does not reject such a message: a TSIG that is not the last record on the wire raises \"misplaced or corrupt TSIG\", but the error is caught, reported as a warning, and the record is left in the packet. RFC 8945 section 5.2 requires the message to be dropped.\n\nThe recursion is reached only when the decoded TSIG carries an empty MAC, since a MAC recovered from the wire short-circuits the signing step. It is reached only from code that re-encodes a message it decoded, such as a forwarder or a proxy. A decoded message that is never re-encoded is unaffected. Message direction does not matter: a query reaches the same path as a response.\n\nEach cycle re-encodes the whole message, so fewer than 100 bytes on the wire exhaust available memory and terminate the process."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-674","description":"CWE-674 Uncontrolled Recursion","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-09-01T23:14:52.133Z","orgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","shortName":"CPANSec"},"references":[{"url":"https://metacpan.org/release/NLNETLABS/Net-DNS-1.56/source/lib/Net/DNS/RR/TSIG.pm#L245-262"},{"url":"https://metacpan.org/release/NLNETLABS/Net-DNS-1.56/source/lib/Net/DNS/RR/TSIG.pm#L62-73"},{"url":"https://datatracker.ietf.org/doc/html/rfc8945#section-5.2"},{"tags":["issue-tracking"],"url":"https://rt.cpan.org/Ticket/Display.html?id=181125"},{"tags":["release-notes"],"url":"https://metacpan.org/release/NLNETLABS/Net-DNS-1.57/changes"}],"solutions":[{"lang":"en","value":"Upgrade to Net-DNS 1.57 or later."}],"source":{"discovery":"UNKNOWN"},"title":"Net::DNS versions before 1.57 for Perl allow memory exhaustion via unbounded recursion in sig_data when re-encoding a message with a misplaced TSIG record","workarounds":[{"lang":"en","value":"For deployments that are not able to upgrade to Net-DNS 1.57, reject a decoded message before re-encoding it if a TSIG record appears anywhere but the final position of the additional section."}],"x_generator":{"engine":"cpansec-cna-tool 0.1"}}},"cveMetadata":{"assignerOrgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","assignerShortName":"CPANSec","cveId":"CVE-2026-81928","datePublished":"2026-09-01T23:14:52.133Z","dateReserved":"2026-08-27T18:31:50.335Z","dateUpdated":"2026-09-01T23:14:52.133Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-02 00:18:26","lastModifiedDate":"2026-09-02 00:18:26","problem_types":["CWE-674","CWE-674 CWE-674 Uncontrolled Recursion"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"81928","Ordinal":"1","Title":"Net::DNS versions before 1.57 for Perl allow memory exhaustion v","CVE":"CVE-2026-81928","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"81928","Ordinal":"1","NoteData":"Net::DNS versions before 1.57 for Perl allow memory exhaustion via unbounded recursion in sig_data when re-encoding a message with a misplaced TSIG record.\n\nsig_data signs a message by re-encoding it, and removes TSIG records only from the additional section. A TSIG decoded into the answer or authority section survives that step and is signed again, so encoding re-enters sig_data with no termination condition. Decoding does not reject such a message: a TSIG that is not the last record on the wire raises \"misplaced or corrupt TSIG\", but the error is caught, reported as a warning, and the record is left in the packet. RFC 8945 section 5.2 requires the message to be dropped.\n\nThe recursion is reached only when the decoded TSIG carries an empty MAC, since a MAC recovered from the wire short-circuits the signing step. It is reached only from code that re-encodes a message it decoded, such as a forwarder or a proxy. A decoded message that is never re-encoded is unaffected. Message direction does not matter: a query reaches the same path as a response.\n\nEach cycle re-encodes the whole message, so fewer than 100 bytes on the wire exhaust available memory and terminate the process.","Type":"Description","Title":"Net::DNS versions before 1.57 for Perl allow memory exhaustion v"}]}}}