Skip to main content
Mallory
HighVulnerability

CVE-2026-1519: DNSSEC NSEC3 CPU Exhaustion in ISC BIND 9

Published Mar 25, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS7.5High · v3.1
EPSS1.7%78th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-1519CWE-400

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
Internet Systems ConsortiumBindapplication
FAQ

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.
Activity feed

Recent activity

47 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 14, 2026Rocky Linux 9.2 [CIQ] Security Update: bind / bind-chroot / bi... | Tenable®A vulnerability addressed by CIQ advisory ciqsa-2026_1799 for BIND packages in Rocky Linux 9.2. Its technical cause and impact are unspecified. Updated packages are available; detection relies on self-reported package versions, not vulnerability testing.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : bind (EulerOS-SA-2026-4628) | Tenable®A CPU-exhaustion vulnerability affecting BIND resolvers performing DNSSEC validation on maliciously crafted zones. Authoritative-only servers are generally unaffected, except in circumstances where they perform recursive queries. Updated EulerOS bind packages are available.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : bind (EulerOS-SA-2026-4686) | Tenable®A CPU-exhaustion vulnerability affecting BIND resolvers performing DNSSEC validation on maliciously crafted zones. Authoritative-only servers are generally unaffected, except where they perform recursive queries. Updated EulerOS Virtualization bind packages are available; Nessus checks versions without testing exploitation.Read more ↗tenable nessus pluginsNews · Oct 19, 2026Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 L... | Tenable®Listed in an Ubuntu BIND 9 security update. No CVE-specific technical details are supplied; the bulletin's collective exploit-availability statement does not identify individual exploitable CVEs.Read more ↗
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity17Community discussion across Reddit, Mastodon, and other social sources.