CVE-2026-1519: DNSSEC NSEC3 CPU Exhaustion in ISC BIND 9
- Vendor
- Internet Systems Consortium
CVE-2026-1519 is a resource-exhaustion vulnerability in ISC BIND 9 DNSSEC validation. Incorrect handling of insecure delegation validation can cause excessive NSEC3 iterations when a resolver encounters a maliciously crafted DNS zone, consuming excessive CPU and potentially causing denial of service. Affected versions are 9.11.0–9.16.50, 9.18.0–9.18.46, 9.20.0–9.20.20, 9.21.0–9.21.19, 9.11.3-S1–9.16.50-S1, 9.18.11-S1–9.18.46-S1, and 9.20.9-S1–9.20.20-S1. Authoritative-only servers are generally unaffected, except in circumstances where they perform recursive queries.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
A remote, unauthenticated attacker can exhaust CPU resources on an affected DNSSEC-validating resolver, delaying or preventing legitimate DNS resolution and disrupting services dependent on it. The vulnerability has high availability impact, with no identified confidentiality or integrity impact. Code execution, privilege escalation, and DNSSEC validation bypass are not established consequences of this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Restrict recursive DNS access to trusted clients and disable recursion on authoritative-only servers where it is unnecessary. These restrictions reduce exposure but do not eliminate the risk if a trusted client causes resolution of a malicious zone. Where operationally acceptable, temporarily disabling recursive service or DNSSEC validation removes the affected processing condition; disabling validation sacrifices DNSSEC protection and should not replace patching. Monitor resolver CPU utilization and DNS response latency for resource exhaustion.
Remediation
Patch, then assume compromise.
Upgrade to a supported BIND release containing the vendor's fix, or install the corrected BIND packages supplied by the operating-system vendor. Exact upstream fixed release numbers are not available in the supplied vulnerability details. Ubuntu deployments should apply USN-8929-1; other distributions and products should apply their corresponding BIND security updates. For bundled deployments, update the containing product's packages or images rather than relying solely on upstream version comparisons, because vendor packages may contain backported fixes.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-1519 exploited in the wild?
- As of Nov 14, 2026, Mallory has no reports of CVE-2026-1519 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-1519?
- As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-1519.
- Is there a patch for CVE-2026-1519?
- Upgrade to a supported BIND release containing the vendor's fix, or install the corrected BIND packages supplied by the operating-system vendor. Exact upstream fixed release numbers are not available in the supplied vulnerability details.
- What products are affected by CVE-2026-1519?
- Internet Systems Consortium Bind.
- How severe is CVE-2026-1519?
- CVE-2026-1519 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.7% (78th percentile) as of Nov 14, 2026.
Recent activity
47 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.