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 Details
- CVSS 3.1 Base Score: 5.9
- CVSS 3.1 Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade bind | Sep 28, 2026 | Sep 16, 2026 |
| Amazon_linux_2023 | — | Upgrade bind-develUpgrade bind-dnssec-utilsUpgrade bind-debuginfoUpgrade bind-libsUpgrade bind-utilsUpgrade bind-libs-debuginfoUpgrade bind-licenseUpgrade bindUpgrade bind-chrootUpgrade bind-debugsourceUpgrade bind-utils-debuginfoUpgrade bind-dnssec-utils-debuginfoUpgrade bind-doc | Sep 30, 2026 | Sep 16, 2026 |
| Debian | — | Upgrade bind9 | Sep 21, 2026 | Sep 16, 2026 |
| Freebsd | — | Upgrade bind920 | Oct 5, 2026 | Oct 4, 2026 |
| Redhat_linux | — | No solution exists | Sep 18, 2026 | Sep 16, 2026 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub