Skip to main content
Mallory
HighVulnerability

CVE-2026-13204: BIND DNSSEC Validation Assertion Failure with Mixed NSEC and NSEC3 Records

Published Jul 22, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days18 mentions · peak 4 in a dayToday
CVSS7.5High · v3.1
EPSS0.52%45th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-13204CWE-617 · Reachable Assertion

CVE-2026-13204 is a reachable assertion vulnerability in BIND 9 DNSSEC validation. When a provably insecure domain is covered by both NSEC and NSEC3 records at its parent, but an RRSIG exists for only one of those record types, validating the proof can trigger an assertion failure and terminate the DNS server process. Affected versions are 9.11.0–9.18.50, 9.20.0–9.20.24, 9.21.0–9.21.23, 9.11.3-S1–9.18.50-S1, and 9.20.9-S1–9.20.24-S1. Products embedding affected BIND versions, including F5 BIG-IP DNS, may also be affected.

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 cause the BIND DNS server process to terminate during DNSSEC validation, resulting in denial of service for clients relying on that server. The vulnerability does not establish arbitrary code execution, information disclosure, cache poisoning, or DNSSEC validation bypass.

Mitigation

If you can’t patch tonight, do this now.

On F5 BIG-IP DNS, disable the BIND server by setting "Use BIND Server on BIG-IP" to Disabled in the applicable DNS profile, or restrict DNS recursion. Disabling BIND can affect deployments using it as a fallback resolution method. Restrict recursive DNS access to trusted clients where feasible, although this does not eliminate exposure if permitted clients trigger resolution of attacker-controlled DNS data. No general BIND-specific workaround is identified.

Remediation

Patch, then assume compromise.

Install vendor-provided BIND security updates for the applicable operating system or embedded product. Available corrected packages include Debian trixie bind9 1:9.20.26-1~deb13u1 and Ubuntu bind9 1:9.20.24-1ubuntu0.4 for Ubuntu 26.04 LTS, 1:9.18.39-0ubuntu0.24.04.8 for Ubuntu 24.04 LTS, and 1:9.18.39-0ubuntu0.22.04.7 for Ubuntu 22.04 LTS. Distribution packages may contain backported fixes despite retaining an upstream version within the affected ranges. For F5 BIG-IP DNS, install a release explicitly identified as fixed for the relevant branch; no fixed release is identified in bulletin K000163212.

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-13204 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-13204 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-13204?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-13204.
Is there a patch for CVE-2026-13204?
Install vendor-provided BIND security updates for the applicable operating system or embedded product. Available corrected packages include Debian trixie bind9 1:9.20.26-1~deb13u1 and Ubuntu bind9 1:9.20.24-1ubuntu0.4 for Ubuntu 26.04 LTS, 1:9.18.39-0ubuntu0.24.04.8 for Ubuntu 24.04 LTS, and 1:9.18.39-0ubuntu0.22.04.7 for Ubuntu 22.04 LTS.
What products are affected by CVE-2026-13204?
Internet Systems Consortium Bind.
How severe is CVE-2026-13204?
CVE-2026-13204 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.52% (45th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

View more in app →
+55 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 activity5Community discussion across Reddit, Mastodon, and other social sources.