CVE-2026-19941

published 16 Sep 2026 · updated 25 Oct 2026

checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof

5.9MediumCVSS 5.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ISCBIND>=9.11.0 <=9.18.50, >=9.11.3-S1 <=9.18.50-S1, >=9.20.0 <=9.20.27, >=9.20.9-S1 <=9.20.27-S1, >=9.21.0 <=9.21.25

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in BIND, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-19941 severity on Zeptric[![CVE-2026-19941](https://zeptric.io/badge/cve/CVE-2026-19941.svg)](https://zeptric.io/cve/CVE-2026-19941)