Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
HIGH severity

CVE-2026-13321

HIGH

CVE-2026-13321 is a high-severity (CVSS 8.6) CWE-346 vulnerability. No vendor fix is recorded yet; mitigation options are listed below.

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,…

Published
Updated
Affected
—
Patched
—
Exploits
None indexed
Exploitation data as of Oct 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-13321.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk-0.02%
Lower risk than most CVEs10th percentile — riskier than 10% of all scored CVEsHighest risk
0.00%0.24%0.48%0.72%0.2%0.2%0.2%0.2%Aug 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-13321 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 393,867 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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.

Detection & mitigation playbook

Vulnerability
  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Remediation status

    No fixed release is recorded for CVE-2026-13321 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

An attacker controlling any DNSSEC-signed zone can craft NSEC records that span into victim zones, enabling cross-zone cache poisoning with authenticated denial-of-service responses (AD=1).

Workaround published by Red Hat
Disclaimer: The following mitigation notes are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. ISC states no workarounds exist. Until patched, restrict the resolver to authorized client networks and deploy separate resolvers per trust zone. Memory hardening and auth controls don't apply — this is a DNS protocol logic error using validly-signed records.
Source: Red Hat security advisory for CVE-2026-13321 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 10bind-32:9.18.33-15.el10_2.10RHSA-2026:55437
Red Hat Enterprise Linux 7 Extended Lifecycle Supportbind-32:9.11.4-26.P2.el7_9.21RHSA-2026:60383
Red Hat Enterprise Linux 8bind9.16-32:9.16.23-0.22.el8_10.12RHSA-2026:54509
Red Hat Enterprise Linux 8bind-32:9.11.36-16.el8_10.14RHSA-2026:54654
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Supportbind9.16-32:9.16.23-0.7.el8_6.11RHSA-2026:80501
Red Hat Enterprise Linux 8.8 Telecommunications Update Servicebind9.16-32:9.16.23-0.14.el8_8.9RHSA-2026:79160
Red Hat Enterprise Linux 9bind-32:9.16.23-40.el9_8.8RHSA-2026:54510
Red Hat Enterprise Linux 9bind9.18-32:9.18.29-14.el9_8.8RHSA-2026:55442

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-13321 in your dependencies?

Find it across , including transitive dependencies.

CVE-2026-13321: Origin Validation Error (High 8.6)