PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-64194 NLNETLABS CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-20T19:17:30.157Z and has not been modified since then. Net::DNS versions through 1.55 for Perl allow Denial of Service via deep DNS compression pointer chains due to unlimited recursion in Net::DNS::DomainName::decode. The guard `$link < $offset` prevents forward and circular chains, but still allows arbitrarily long backward chains. A crafted packet can chain two-byte compression pointers so that each one points two bytes earlier than the previous, producing a chain length of `offset / 2`. For the 14-bit pointer field (max offset 16383) this gives up to ~8191 recursive frames. For a TCP DNS message the limit is the 16-bit length field (~32767 frames). Perl's default C stack handles only a few thousand frames; beyond that the process receives SIGSEGV or similar, which is a denial-of-service for any application parsing untrusted DNS data. The vulnerability is triggered by `Net::DNS::Packet->new(> i.e. any point where the library decodes a DNS message from the network. Administrators and users of Net::DNS version 1.55 or earlier for Perl should take defensive actions to prevent potential Denial of Service attacks. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Vendor
NLNETLABS
Product
Net::DNS
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-20
Original CVE updated
2026-08-30
Advisory published
2026-07-20
Advisory updated
2026-08-30

Who should care

Administrators and users of Net::DNS version 1.55 or earlier for Perl should take defensive actions to prevent potential Denial of Service attacks. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed and review compensating controls for exposed systems while remediation is scheduled and verified. Additionally, they should check relevant monitoring, detection, and logs for exposed assets that need extra review and track exceptions, retest remediated assets, and close the item only after evidence is documented. Affected operators, platforms, vulnerability-management, and security teams should prioritize defensive actions to address the Denial of Service vulnerability in Net::DNS versions through 1.55 for Perl.

Technical summary

Net::DNS versions through 1.55 for Perl allow Denial of Service via deep DNS compression pointer chains due to unlimited recursion in Net::DNS::DomainName::decode. The guard `$link < $offset` prevents forward and circular chains, but still allows arbitrarily long backward chains. A crafted packet can chain two-byte compression pointers so that each one points two bytes earlier than the previous, producing a chain length of `offset / 2`. For the 14-bit pointer field (max offset 16383) this gives up to ~8191 recursive frames. For a TCP DNS message the limit is the 16-bit length field (~32767 frames). Perl's default C stack handles only a few thousand frames; beyond that the process receives SIGSEGV or similar, which is a denial-of-service for any application parsing untrusted DNS data. The vulnerability is triggered by `Net::DNS::Packet->new(> i.e. any point where the library decodes a DNS message from the network. The per-offset cache (`$cache`) is populated at the start of each call and short-circuits only re-traverses of the same offset - the initial descent through a fresh chain still recurses at full depth.

Defensive priority

High-priority defensive actions are required to address the Denial of Service vulnerability in Net::DNS versions through 1.55 for Perl.

Recommended defensive actions

  • Implement compensating controls to detect and prevent potentially malicious DNS traffic
  • Monitor DNS traffic for unusual patterns
  • Restrict access to DNS servers
  • Update Net::DNS to version 1.56 or later
  • Verify and limit recursive DNS queries

Evidence notes

Evidence from the CVE Program and NVD suggests a Denial of Service vulnerability exists in Net::DNS versions through 1.55 for Perl. The CVE record and NVD detail provide limited information about the vulnerability, but defenders should verify the affected scope, severity, and vendor guidance. The vulnerability is triggered by Net::DNS::Packet->new(> i.e. any point where the library decodes a DNS message from the network. Further details are limited, and defenders should review the official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-64194 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-64194

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-64194 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64194

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://metacpan.org/release/NLNETLABS/Net-DNS-1.55_01/changes

    9b29abf9-4ab0-4765-b253-1875cd9b441e

  • Source reference

    Unverified legacy reference

    URL: https://www.net-dns.org/blog/

    9b29abf9-4ab0-4765-b253-1875cd9b441e

  • Source reference

    Unverified legacy reference

    URL: https://lists.debian.org/debian-lts-announce/2026/08/msg00052.html

    af854a3a-2127-422b-91ae-364da2661108

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.