CVE-2026-19941: CWE-345 Insufficient Verification of Data Authenticity in ISC BIND 9
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.
AI Analysis
Technical Summary
The vulnerability arises from insufficient verification of data authenticity (CWE-345) in ISC BIND 9's DNS resolver component. Specifically, a named resolver may incorrectly accept an inapplicable NSEC record as valid proof that no wildcard DNS record exists in a zone. This can be exploited by an attacker positioned at the same or an upstream zone level to conceal the existence of a victim's wildcard record, potentially impacting DNS resolution behavior. The affected versions include 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and their S1 variants. The CVSS v3.1 base score is 5.9, reflecting a medium severity with network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact.
Potential Impact
An attacker with the ability to provide DNS responses at the same or upstream zone level can exploit this vulnerability to mask the existence of wildcard DNS records. This could lead to DNS resolution inconsistencies or manipulation where legitimate wildcard records are hidden, potentially affecting DNS-based services relying on these records. There is no direct confidentiality or availability impact reported, but integrity of DNS data can be compromised.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Users should monitor ISC advisories for updates and apply patches once available. Until then, consider restricting DNS response sources and monitoring DNS behavior for anomalies related to wildcard record resolution.
CVE-2026-19941: CWE-345 Insufficient Verification of Data Authenticity in ISC BIND 9
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.
CVSS v3.1
Score 5.9medium
Affected software
ISC
BIND 9
pkg:github/isc/bind9Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from insufficient verification of data authenticity (CWE-345) in ISC BIND 9's DNS resolver component. Specifically, a named resolver may incorrectly accept an inapplicable NSEC record as valid proof that no wildcard DNS record exists in a zone. This can be exploited by an attacker positioned at the same or an upstream zone level to conceal the existence of a victim's wildcard record, potentially impacting DNS resolution behavior. The affected versions include 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and their S1 variants. The CVSS v3.1 base score is 5.9, reflecting a medium severity with network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact.
Potential Impact
An attacker with the ability to provide DNS responses at the same or upstream zone level can exploit this vulnerability to mask the existence of wildcard DNS records. This could lead to DNS resolution inconsistencies or manipulation where legitimate wildcard records are hidden, potentially affecting DNS-based services relying on these records. There is no direct confidentiality or availability impact reported, but integrity of DNS data can be compromised.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Users should monitor ISC advisories for updates and apply patches once available. Until then, consider restricting DNS response sources and monitoring DNS behavior for anomalies related to wildcard record resolution.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- isc
- Date Reserved
- 2026-08-15T14:30:38.165Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aaaa16f55bf5e2cf5b35d4c
Added to database: 09/16/2026, 14:02:23 UTC
Last enriched: 09/16/2026, 14:31:36 UTC
Last updated: 09/17/2026, 00:17:16 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.