CVE-2026-5946: BIND 9 `named` Assertion Failure Vulnerability
Multiple flaws in BIND 9's `named` component, specifically versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.48, 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.48-S1, and 9.20.9-S1 through 9.20.22-S1, can be exploited by sending specially crafted DNS requests with non-`IN` CLASS or meta-classes, leading to assertion failures and potential denial-of-service.
CVE-2026-5946 identifies multiple vulnerabilities within the named component of BIND 9, arising from improper handling of DNS messages employing a CLASS other than Internet (IN), such as CHAOS or HESIOD, or DNS messages with meta-classes (ANY or NONE) in the question section. An attacker can trigger these flaws by sending specially crafted DNS requests to a vulnerable BIND 9 server. The affected code paths include recursion, dynamic updates (UPDATE), zone change notifications (NOTIFY), and processing of IN-specific record types within non-IN data. Successful exploitation can lead to assertion failures in named, potentially causing a denial-of-service condition. The vulnerability impacts BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.48, 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.48-S1, and 9.20.9-S1 through 9.20.22-S1.
Attack Chain
- The attacker identifies a vulnerable BIND 9 server.
- The attacker crafts a malicious DNS request. This request leverages a DNS CLASS other than
IN, such asCHAOS, or includes meta-classes such asANYorNONEin the question section. - The attacker sends the crafted DNS request to the target BIND 9 server.
- The
namedprocess receives and parses the malicious DNS request. - Due to the unexpected CLASS or meta-class, the
namedprocess enters a vulnerable code path during recursion, dynamic updates, zone change notifications, or processing ofIN-specific record types in non-INdata. - Within the vulnerable code path, the
namedprocess attempts an invalid operation based on the malicious request. - This invalid operation triggers an assertion failure within the
namedprocess. - The assertion failure may cause the
namedprocess to terminate or become unstable, resulting in a denial-of-service.
Impact
Successful exploitation of CVE-2026-5946 leads to assertion failures within the named process, causing potential instability or termination of the service. This results in a denial-of-service condition, disrupting DNS resolution services for affected networks and users. The severity of the impact depends on the role of the affected BIND 9 server; critical infrastructure DNS servers experiencing this issue can cause widespread outages.
Recommendation
- Upgrade BIND 9 to a patched version (>= 9.16.51, >= 9.18.49, >= 9.20.23, >= 9.21.22) to remediate CVE-2026-5946.
- Deploy the Sigma rule “Detect DNS queries with non-IN class” to identify potentially malicious DNS requests targeting this vulnerability.
- Monitor DNS server logs for assertion failures in the
namedprocess, which may indicate exploitation attempts related to CVE-2026-5946. - Consider implementing rate limiting and request filtering to mitigate the impact of malicious DNS requests.
Detection coverage 2
Detect DNS queries with non-IN class
lowDetects DNS queries with a CLASS other than IN, potentially indicating an attempt to trigger CVE-2026-5946.
Detect named process crashes due to assertion failures
mediumDetects `named` process crashes in system logs that are caused by assertion failures, possibly related to CVE-2026-5946.
Detection queries are available on the platform. Get full rules →