Skip to main content
Mallory
HighVulnerability

CVE-2026-13321: DNSSEC Validation Bypass in BIND via Out-of-Zone NSEC Next Domain Name

Published Jul 22, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days25 mentions · peak 4 in a dayToday
CVSS8.6High · v3.1
EPSS0.22%12th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-13321CWE-345

CVE-2026-13321 is a DNSSEC validation vulnerability in the BIND resolver. The resolver accepts validly signed NSEC records whose Next Domain Name field points outside the signer's zone, failing to enforce the zone boundary when evaluating authenticated denial-of-existence proofs. This permits DNSSEC validation bypass and undermines the integrity of resolver trust decisions. Affected versions are BIND 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; distribution packages may contain backported fixes.

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.

Remote exploitation can compromise DNS response integrity by causing a resolver to accept signed NSEC data with an invalid cross-zone scope. The vulnerability defeats DNSSEC validation boundaries without requiring a forged cryptographic signature. Its CVSS v3 assessment is 8.6, with high integrity impact and changed scope; no direct confidentiality or availability impact is assessed.

Mitigation

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

No vulnerability-specific temporary workaround is identified. Restrict recursive DNS access to trusted clients to reduce exposure, but do not treat access restrictions as a substitute for patching: permitted recursive queries can still cause a resolver to encounter malicious authoritative responses.

Remediation

Patch, then assume compromise.

Install vendor security updates that reject out-of-zone NSEC next owner names. Debian fixed bind9 versions include 1:9.16.50-1~deb11u6 for bullseye, 1:9.18.49-1~deb12u2 for bookworm, and 1:9.20.26-1~deb13u1 for trixie. Ubuntu security updates include 1:9.20.24-1ubuntu0.4 for 26.04 LTS, 1:9.18.39-0ubuntu0.24.04.8 for 24.04 LTS, and 1:9.18.39-0ubuntu0.22.04.7 for 22.04 LTS. For other platforms, apply the corresponding BIND security update. Evaluate distribution package revisions rather than upstream version numbers alone because fixes are backported.

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-13321 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-13321 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-13321?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-13321.
Is there a patch for CVE-2026-13321?
Install vendor security updates that reject out-of-zone NSEC next owner names. Debian fixed bind9 versions include 1:9.16.50-1~deb11u6 for bullseye, 1:9.18.49-1~deb12u2 for bookworm, and 1:9.20.26-1~deb13u1 for trixie.
What products are affected by CVE-2026-13321?
Internet Systems Consortium Bind.
How severe is CVE-2026-13321?
CVE-2026-13321 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 0.22% (12th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

104 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 16, 2026EulerOS Virtualization 2.10.1 : bind (EulerOS-SA-2026-4984) | Tenable®A vulnerability covered by the BIND security update EulerOS-SA-2026-4984 for Huawei EulerOS Virtualization 2.10.1. It is identified as the CVSS score source; the supplied CVSS v3 vector indicates network exploitation without privileges or user interaction, changed scope, and high integrity impact. A patch publication date of November 17, 2026 is listed.Read more ↗tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.10.0 : bind (EulerOS-SA-2026-5024) | Tenable®Listed in the BIND security update for EulerOS Virtualization 2.10.0, advisory EulerOS-SA-2026-5024. It is the stated source of the displayed CVSS vector, which indicates network exploitation without privileges or user interaction, changed scope, and high integrity impact. The underlying vulnerability mechanism is not described.Read more ↗tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.12.1 : bind (EulerOS-SA-2026-4862) | Tenable®A vulnerability included in EulerOS-SA-2026-4862 for bind packages on EulerOS Virtualization 2.12.1 and identified as the advisory's CVSS score source. The displayed CVSS v3 vector indicates network exploitation without privileges or user interaction, with high integrity impact and changed scope.Read more ↗tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.12.0 : bind (EulerOS-SA-2026-4923) | Tenable®A bind vulnerability addressed by EulerOS-SA-2026-4923 for EulerOS Virtualization 2.12.0. It is identified as the source of the advisory's CVSS vector, which indicates network attackability without privileges or user interaction and high integrity impact.Read more ↗
+74 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 activity13Community discussion across Reddit, Mastodon, and other social sources.