Multiple flaws have been identified in named related to the handling of DNS messages whose CLASS is not Internet (IN) — for example, CHAOS or HESIOD, or DNS messages that specify meta-classes (ANY or NONE) in the question section. Specially crafted requests reaching the affected code paths — recursion, dynamic updates (UPDATE), zone change notifications (NOTIFY), or processing of IN-specific record types in non-IN data — can cause assertion failures in named.
This issue affects 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.
CVE-2026-5946
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. NVD baseline CVSS 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 76.0%
- KEV
- Not listed
Published
May 20, 2026
Last Modified
June 30, 2026
Advisory Details (4)
Auto-updated Jun 6, 2026Vendor Advisories for CVE-2026-5946(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-5946Microsoft Security Response Center (MSRC)High
Invalid handling of CLASS != IN
- RHSA-2026:20334Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- GHSA-cqgq-ff3f-rj7rGitHub Security AdvisoriesHigh
Multiple flaws have been identified in `named` related to the handling of DNS messages whose...
Patch Availability(7)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | bind9-utils (1:9.20.18-1ubuntu2.1) @ resolute | 2026-06-29 | ubuntu |
| redhat | bind-32:9.11.36-16.el8_10.8 | 2026-06-08 | redhat |
| redhat | bind-32:9.18.33-15.el10_2.2 | 2026-06-08 | redhat |
| redhat | bind-32:9.16.23-40.el9_8.2 | 2026-06-08 | redhat |
| redhat | bind9.18-32:9.18.29-14.el9_8.2 | 2026-06-08 | redhat |
| redhat | bind9.16-32:9.16.23-0.22.el8_10.6 | 2026-06-04 | redhat |
| redhat | bind-main-9.18.49-1.hum1 | 2026-05-21 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(6)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(6)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
- Red HatRHSA-2026:23360IMPORTANT2026-05-21
RHSA-2026:23360 — Important
- Red HatRHSA-2026:24338IMPORTANT2026-05-21
RHSA-2026:24338 — Important
- Red HatRHSA-2026:24339IMPORTANT2026-05-21
RHSA-2026:24339 — Important
- Red HatRHSA-2026:24367IMPORTANT2026-05-21
RHSA-2026:24367 — Important
- Red HatRHSA-2026:24368IMPORTANT2026-05-21
RHSA-2026:24368 — Important
- UbuntuUSN-8293-1MEDIUM
Bind vulnerabilities
Data Freshness Timeline
(refreshed 14× in last 7d / 97× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 189 total refreshes for this CVE.
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 20:29 UTCEG score recompute
- 2026-06-29 20:29 UTCVendor advisory
- 2026-06-29 20:29 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 09:27 UTCEG score recompute
- 2026-06-28 09:27 UTCVendor advisory
- 2026-06-28 09:27 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 20:48 UTCEG score recompute
- 2026-06-27 20:48 UTCVendor advisory
- 2026-06-27 20:48 UTCGHSA enrichment
- 2026-06-27 08:11 UTCEG score recompute
- 2026-06-27 08:11 UTCVendor advisory
- 2026-06-27 08:11 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:34 UTCEG score recompute
- 2026-06-26 19:34 UTCVendor advisory
- 2026-06-26 19:34 UTCGHSA enrichment
- 2026-06-26 04:13 UTCEG score recompute
- 2026-06-26 04:13 UTCVendor advisory
- 2026-06-26 04:13 UTCGHSA enrichment
- 2026-06-25 15:36 UTCEG score recompute
- 2026-06-25 15:36 UTCVendor advisory
- 2026-06-25 15:36 UTCGHSA enrichment
- 2026-06-25 13:50 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 00:03 UTCEG score recompute
- 2026-06-18 00:03 UTCVendor advisory
- 2026-06-18 00:03 UTCGHSA enrichment
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 11:26 UTCEG score recompute
- 2026-06-17 11:26 UTCVendor advisory
- 2026-06-17 11:26 UTCGHSA enrichment
- 2026-06-16 20:13 UTCEG score recompute
- 2026-06-16 20:13 UTCVendor advisory
- 2026-06-16 20:13 UTCGHSA enrichment
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-16 04:53 UTCEG score recompute
- 2026-06-16 04:53 UTCVendor advisory
- 2026-06-16 04:53 UTCGHSA enrichment
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 15:51 UTCEG score recompute
- 2026-06-15 15:51 UTCVendor advisory
- 2026-06-15 15:51 UTCGHSA enrichment
- 2026-06-14 23:41 UTCEG score recompute
- 2026-06-14 23:41 UTCVendor advisory
- 2026-06-14 23:41 UTCGHSA enrichment
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 11:04 UTCEG score recompute
- 2026-06-14 11:04 UTCVendor advisory
- 2026-06-14 11:04 UTCGHSA enrichment
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 22:28 UTCEG score recompute
- 2026-06-13 22:28 UTCVendor advisory
- 2026-06-13 22:28 UTCGHSA enrichment
- 2026-06-13 04:59 UTCEG score recompute
- 2026-06-13 04:59 UTCVendor advisory
- 2026-06-13 04:59 UTCGHSA enrichment
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 16:22 UTCEG score recompute
- 2026-06-12 16:22 UTCVendor advisory
- 2026-06-12 16:22 UTCGHSA enrichment
- 2026-06-12 03:44 UTCEG score recompute
- 2026-06-12 03:44 UTCVendor advisory
- 2026-06-12 03:44 UTCGHSA enrichment
- 2026-06-11 15:07 UTCEG score recompute
- 2026-06-11 15:07 UTCVendor advisory
- 2026-06-11 15:06 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-5946?
When was CVE-2026-5946 disclosed?
Is CVE-2026-5946 actively exploited?
What is the CVSS score of CVE-2026-5946?
How do I remediate CVE-2026-5946?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-5946
Is Your Infrastructure Affected by CVE-2026-5946?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.