CVE-2026-64194: Net::DNS vulnerability
CVE-2026-64194 affects Net::DNS. Net::DNS::DomainName::decode follows RFC 1035 compression pointers by recursing into itself with no depth limit.
What happened
A security weakness in Net::DNS is being tracked as CVE-2026-64194. CVE-2026-64194 affects Net::DNS. 55 for Perl allow Denial of Service via deep DNS compression pointer chains.
Net::DNS::DomainName::decode follows RFC 1035 compression pointers by recursing into itself with no depth limit. Net::DNS::DomainName::decode follows RFC 103. Net::DNS versions through 1.
It is possible to construct a name which saturates the call stack (at least with larger TCP responses), leading to a potential Denial of Service.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
Net::DNS versions through 1.
55 for Perl allow Denial of Service via deep DNS compression pointer chains.
The guard `$link new(\$wire)` i.
A security weakness in Net::DNS is being tracked as CVE-2026-64194. Net::DNS::DomainName::decode follows RFC 1035 compression pointers by recursing into itself with no depth limit. It is possible to construct a name which saturates the call stack (at least with larger TCP responses), leading to a potential Denial of Service. The guard `$link new(\$wire)` i. any point where the l. The issue currently carries a HIGH 7.5 severity signal in the available reporting.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
Net::DNS is present and the vulnerable function or code path is reachable in normal application use.
attacker-controlled input or the relevant workflow reaches the the reported vulnerability condition described in the advisory.
the the reported vulnerability condition is triggered inside Net::DNS, creating the security boundary failure described by the advisory.
successful exploitation reaches the confidentiality, integrity or availability impact described in the vendor or vulnerability record.
Why this matters to you
CVE-2026-64194 matters because the practical risk is not the score alone — it is whether Net::DNS through 1 exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is HIGH 7.5. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of Net::DNS through 1.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for Net::DNS through 1.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.