This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-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.29, 9.21.26, or 9.20.29-S1.
Vendor Workaround
No workarounds known.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 16 Sep 2026 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. | |
| Title | checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof | |
| First Time appeared |
Isc
Isc bind |
|
| Weaknesses | CWE-345 | |
| CPEs | cpe:2.3:a:isc:bind:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Isc
Isc bind |
|
| References |
| |
| Metrics |
cvssV3_1
|
MITRE
Status: PUBLISHED
Assigner: isc
Published:
Updated: 2026-09-16T13:52:49.400Z
Reserved: 2026-08-15T14:30:38.165Z
Link: CVE-2026-19941
Vulnrichment
No data.
NVD
Status : Received
Published: 2026-09-16T14:17:05.160
Modified: 2026-09-16T14:17:05.160
Link: CVE-2026-19941
Redhat
No data.
OpenCVE Enrichment
No data.