{"id":"CVE-2026-19941","title":"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.\nThis…","summary":"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.\nThis…","severity":"medium","cvss":5.9,"cvssVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","cwe":["CWE-345","CWE-346"],"vendor":"ISC","product":"BIND 9","affected":["bind_9 >= 9.11.0 <= 9.18.50","bind_9 >= 9.20.0 <= 9.20.27","bind_9 >= 9.21.0 <= 9.21.25","bind_9 >= 9.11.3-S1 <= 9.18.50-S1","bind_9 >= 9.20.9-S1 <= 9.20.27-S1"],"published":"2026-09-16","updated":"2026-09-17","sourceUpdated":"2026-09-17T19:16:42.200","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-19941","references":[{"url":"https://downloads.isc.org/isc/bind9/9.20.29","label":"security-officer@isc.org"},{"url":"https://downloads.isc.org/isc/bind9/9.21.26","label":"security-officer@isc.org"},{"url":"https://kb.isc.org/docs/cve-2026-19941","label":"security-officer@isc.org"},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19941.json"},{"url":"https://access.redhat.com/security/cve/CVE-2026-19941"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535457"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19941"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19941"},{"url":"https://access.redhat.com/errata/RHSA-2026:68279"}],"tags":["nvd","cve.org","csaf","vex","red-hat"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-09-17T18:44:04.658605Z"},"ingestedAt":"2026-09-16T14:57:28.016Z","epss":0.00188,"epssPercentile":0.08653,"patched":["hardened_images"],"slug":"CVE-2026-19941","body":"## Overview\n\nAn 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.\nThis 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n## Vendor advisories\n\n- **Red Hat VEX** · Moderate · affected: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat OpenShift Container Platform 4 · no fix planned: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, … · updated 2026-09-21 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19941.json)\n- **RHSA-2026:68279** · Red Hat · fixed in: Red Hat Hardened Images · released 2026-09-16 · [advisory](https://access.redhat.com/errata/RHSA-2026:68279)","depth":"sunlit","depthScore":32,"depthScoreParts":{"impact":32.5,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}