CVE-2026-13204

Unexpected exit in certain situations with NSEC and NSEC3 both present

Published Jul 22, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof.
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.

Analysis

AI-generated

Technical impact

According to the CVE description, if a provably insecure domain is covered by both NSEC and NSEC3 records at the parent zone, and an RRSIG exists for only one of those records, BIND 9 may terminate unexpectedly during zone validation. The crash is caused by an assertion failure, leading to a denial of service for DNS queries that trigger the validation path. This vulnerability is identified as CWE-617, representing unchecked input validation as justified by the assertion failure described in the CVE text.

Affected Systems

All ISC BIND 9 releases from 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, and 9.21.0 through 9.21.23, as well as the corresponding security‑patched point releases 9.11.3‑S1 through 9.18.50‑S1 and 9.20.9‑S1 through 9.20.24‑S1, are affected when both NSEC and NSEC3 coexist at the parent for an insecure domain.

Risk and Exploitability

Based on the description, the likely attack vector is DNS queries that trigger zone validation. The CVSS score of 7.5 indicates a moderate to high severity. The EPSS score is < 1% and the vulnerability is not listed in the CISA KEV catalog. Attackers are likely to exploit the flaw by issuing DNS queries that force the server to validate a zone containing conflicting NSEC and NSEC3 records. If successful, the BIND server will crash, resulting in temporary loss of availability for the affected zones and potentially broader DNS disruptions.

Remediation

Vendor Solution

Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.26, 9.21.24, or 9.20.26-S1.


Vendor Workaround

No workarounds known.


OpenCVE Recommended Actions

  • Upgrade to the latest patched BIND 9 release (9.20.26, 9.21.24, or 9.20.26‑S1) as soon as possible.
  • Reconfigure or remove zones that simultaneously use NSEC and NSEC3 records at the parent if feasible.
  • Enable monitoring of DNS server logs for assertion failures and establish automatic failover or load balancing to mitigate temporary disruption.

Generated by OpenCVE AI on August 3, 2026 at 23:33 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4725-1 bind9 security update
Debian DSA Debian DSA DSA-6395-1 bind9 security update
Ubuntu USN Ubuntu USN USN-8696-1 Bind vulnerability
Ubuntu USN Ubuntu USN USN-8929-1 Bind vulnerabilities
History
Type Values Removed Values Added
CPEs cpe:2.3:a:isc:bind:*:*:*:*:-:*:*:*
cpe:2.3:a:isc:bind:*:*:*:*:supported_preview:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. 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.
Title Unexpected exit in certain situations with NSEC and NSEC3 both present
First Time appeared Isc
Isc bind
Weaknesses CWE-617
CPEs cpe:2.3:a:isc:bind:*:*:*:*:*:*:*:*
Vendors & Products Isc
Isc bind
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
isc
Published
Updated
Jul 22, 2026, 6:52 PM
Reserved
Jun 24, 2026, 2:12 PM
Status
Analyzed
Published
Jul 22, 2026, 3:16 PM
Modified
Nov 2, 2026, 5:49 PM
Severity
Important
Public date
Jul 22, 2026, 12:00 AM