Skip to main content
Mallory
HighVulnerability

CVE-2026-5946: Assertion-Failure Denial of Service in ISC BIND 9 DNS Class Handling

Published May 20, 2026 · Updated 10 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days9 mentions · peak 4 in a dayToday
CVSS7.5High · v3.1
EPSS1.9%81st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-5946CWE-617 · Reachable Assertion

CVE-2026-5946 comprises multiple reachable assertion flaws in the ISC BIND 9 named DNS server when handling DNS messages with non-Internet classes, such as CHAOS or HESIOD, or questions specifying the meta-classes ANY or NONE. Specially crafted requests can trigger assertion failures through recursion, dynamic updates (UPDATE), zone-change notifications (NOTIFY), or processing of IN-specific record types in non-IN data, terminating named. Affected versions are 9.11.0–9.16.50, 9.18.0–9.18.48, 9.20.0–9.20.22, 9.21.0–9.21.21, 9.11.3-S1–9.16.50-S1, 9.18.11-S1–9.18.48-S1, and 9.20.9-S1–9.20.22-S1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation terminates the named process, causing denial of service for DNS functions served by that process. Both recursive and authoritative service availability can be affected, depending on the reachable processing path. The vulnerability has no established confidentiality or integrity impact.

Mitigation

If you can’t patch tonight, do this now.

Until updates are deployed, limit DNS service exposure to trusted clients where operationally feasible. Restrict recursion to authorized clients, protect dynamic updates with appropriate ACLs and TSIG authentication, and accept NOTIFY messages only from authorized peers. Monitor for assertion failures and use service supervision to restore availability after crashes. These measures reduce exposure or downtime but do not establish complete protection across all affected processing paths.

Remediation

Patch, then assume compromise.

Install a vendor-fixed BIND release or the security-updated packages for the applicable operating-system support stream. Confirmed corrected package builds include RHEL 8 BIND 9.11.36-16.el8_10.8 under RHSA-2026:24339, RHEL 9 BIND 9.16.23-40.el9_8.2 under RHSA-2026:24367, RHEL 9 bind9.18 9.18.29-14.el9_8.2 under RHSA-2026:24368, and RHEL 10 BIND 9.18.33-15.el10_2.2 under RHSA-2026:24338. Use the latest applicable vendor update, which may supersede these builds. Distribution packages may contain backported fixes despite retaining an upstream version within an affected range.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Internet Systems ConsortiumBindapplication
FAQ

Frequently asked questions

Is CVE-2026-5946 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2026-5946 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5946?
As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-5946.
Is there a patch for CVE-2026-5946?
Install a vendor-fixed BIND release or the security-updated packages for the applicable operating-system support stream. Confirmed corrected package builds include RHEL 8 BIND 9.11.36-16.el8_10.8 under RHSA-2026:24339, RHEL 9 BIND 9.16.23-40.el9_8.2 under RHSA-2026:24367, RHEL 9 bind9.18 9.18.29-14.el9_8.2 under RHSA-2026:24368, and RHEL 10 BIND 9.18.33-15.el10_2.2 under RHSA-2026:24338.
What products are affected by CVE-2026-5946?
Internet Systems Consortium Bind.
How severe is CVE-2026-5946?
CVE-2026-5946 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.9% (81st percentile) as of Nov 7, 2026.
Activity feed

Recent activity

67 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : bind (EulerOS-SA-2026-4628) | Tenable®Improper handling of non-IN DNS classes or question-section meta-classes can trigger assertion failures in BIND's named service, causing denial of service. Affected paths include recursion, dynamic updates, zone-change notifications, and processing IN-specific record types within non-IN data. The advisory provides package updates and reports a CVSS v3 base score of 7.5.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : bind (EulerOS-SA-2026-4686) | Tenable®Improper handling of non-IN DNS classes and question-section meta-classes can trigger assertion failures in BIND's named service, causing denial of service. Affected paths include recursion, dynamic updates, zone-change notifications, and processing IN-specific records in non-IN data. Updated EulerOS bind packages are available; the plugin relies on version checks rather than exploitation tests.Read more ↗tenable nessus pluginsNews · Nov 6, 2026RHEL 8 : bind (RHSA-2026:95435) | Tenable®A denial-of-service vulnerability in BIND triggered by specially crafted DNS messages. Security updates are available for affected RHEL 8 packages.Read more ↗tenable nessus pluginsNews · Nov 6, 2026RHEL 6 : bind (RHSA-2026:95727) | Tenable®A BIND vulnerability allowing denial of service through specially crafted DNS messages. Updates are available through RHSA-2026:95727. The advisory-level exploit-availability flag does not establish exploit availability for this specific CVE.Read more ↗
+43 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity10Community discussion across Reddit, Mastodon, and other social sources.