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
Analysis and contextual insights are available on OpenCVE Cloud.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ISC | BIND 9 | unaffected |
|
No data.
No data.
No data available yet.
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.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 22 Jul 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 22 Jul 2026 15:00:00 +0000
| 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
|
MITRE
Status: PUBLISHED
Assigner: isc
Published:
Updated: 2026-07-22T18:52:12.584Z
Reserved: 2026-06-24T14:12:52.934Z
Link: CVE-2026-13204
Vulnrichment
Updated: 2026-07-22T18:52:08.399Z
NVD
No data.
Redhat
No data.
OpenCVE Enrichment
No data.