CVE-2026-13321: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field

Published Jul 21, 2026
·
Updated

DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field

Other sources

The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

MITRE

The resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. An attacker controlling ANY DNSSEC-signed zone can craft NSEC records spanning into victim zones, enabling cross-zone cache poisoning with AD=1 (Authenticated Data flag set)

Red Hat

Affected Software

3 affected componentsFixes available
ISC BIND 9>=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, >=9.20.9-S1<=9.20.24-S1
Microsoft azl3 bind 9.20.23-1<9.20.26-1
9.20.26-1
debian/bind9<=1:9.16.50-1~deb11u2, <=1:9.18.49-1~deb12u1, <=1:9.20.23-1~deb13u1
1:9.16.50-1~deb11u61:9.18.49-1~deb12u21:9.20.26-1~deb13u11:9.20.26-11:9.20.27-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.20.26-1
  2. Upgrade

    Upgrade debian/bind9 to a version that resolves this vulnerability.

    Fixed in 1:9.16.50-1~deb11u6Fixed in 1:9.18.49-1~deb12u2Fixed in 1:9.20.26-1~deb13u1Fixed in 1:9.20.26-1Fixed in 1:9.20.27-1
  3. Upgrade

    Upgrade BIND 9 to a version that resolves this vulnerability.

    Fixed in 9.20.26
  4. Upgrade

    Upgrade BIND 9 to a version that resolves this vulnerability.

    Fixed in 9.21.24
  5. Upgrade

    Upgrade BIND 9 to a version that resolves this vulnerability.

    Fixed in 9.20.26-S1
  6. Compensating control

    Until the patched BIND 9 release is deployed, mitigate cross-zone cache poisoning risk by restricting DNS resolver traffic/queries to trusted upstreams and limiting who can send queries to the affected resolver.

Event History

Jul 21, 2026
Data Sourced
via Red Hat·07:47 PM
DescriptionSeverityAffected Software
Jul 22, 2026
CVE Published
via MITRE·02:16 PM
Data Sourced
via MITRE·02:16 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeakness
Jul 25, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:04 AM
Affected Software
Updated
via Microsoft·08:04 AM
DescriptionSeverity
Aug 19, 2026
Data Sourced
via Launchpad·02:28 PM
Description
Aug 20, 2026
Data Sourced
via Ubuntu·02:27 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·02:28 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-13321?

CVE-2026-13321 has a severity score of 8.6, categorized as high.

2

How do I fix CVE-2026-13321?

To fix CVE-2026-13321, upgrade to a patched version of ISC BIND 9 that is not affected by this vulnerability.

3

What versions of BIND are affected by CVE-2026-13321?

CVE-2026-13321 affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, and 9.21.0 through 9.21.23.

4

What kind of attack is enabled by CVE-2026-13321?

CVE-2026-13321 allows for DNSSEC validation bypass via out-of-zone NSEC next field exploitation.

5

Who is affected by CVE-2026-13321?

Users and administrators of affected versions of ISC BIND 9 are at risk due to CVE-2026-13321.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203