Undefined behavior may result due to a race condition leading to a use-after-free violation. If BIND receives an incoming DNS message signed with SIG(0), it begins work to validate that signature. If, during that validation, the "recursive-clients" limit is reached (as would occur during a query flood), and that same DNS message is discarded per the limit, there is a brief window of time while the SIG(0) validation may attempt to read the now-discarded DNS message. This issue affects BIND 9 versions 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and 9.20.9-S1 through 9.20.22-S1. BIND 9 versions 9.18.28 through 9.18.49 and 9.18.28-S1 through 9.18.49-S1 are NOT affected.
CVE-2026-5947
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. NVD baseline CVSS 7.5; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.9
- EG Score
- 7.5(medium)
- EPSS
- 69.0%
- KEV
- Not listed
Published
May 20, 2026
Last Modified
June 30, 2026
Advisory Details (3)
Auto-updated Jun 6, 2026CVE-2026-5947: SIG(0) validation during query flood may lead to undefined behavior
https://kb.isc.org/docs/cve-2026-5947Vendor Advisories for CVE-2026-5947(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-5947Microsoft Security Response Center (MSRC)High
SIG(0) validation during query flood may lead to undefined behavior
- GHSA-6mm6-m775-chpmGitHub Security AdvisoriesHigh
Undefined behavior may result due to a race condition leading to a use-after-free violation. If...
- RHSA-2026:7412Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | bind9-utils (1:9.20.18-1ubuntu2.1) @ resolute | 2026-06-29 | ubuntu |
| redhat | bind-main-9.18.48-1.1.hum1 | 2026-04-10 | 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(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
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.
Data Freshness Timeline
(refreshed 11× in last 7d / 94× 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-12 05:46 UTCEPSS rescore
- 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-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-30 04:33 UTCNVD updateCVSS v3 → 5.9 · severity → MEDIUM
- 2026-06-29 20:29 UTCEG score recompute
- 2026-06-29 20:29 UTCVendor advisory
- 2026-06-29 20:29 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 09:21 UTCEG score recompute
- 2026-06-28 09:21 UTCVendor advisory
- 2026-06-28 09:21 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:05 UTCEG score recompute
- 2026-06-27 08:05 UTCVendor advisory
- 2026-06-27 08:05 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:07 UTCEG score recompute
- 2026-06-26 04:07 UTCVendor advisory
- 2026-06-26 04:07 UTCGHSA enrichment
- 2026-06-25 15:35 UTCEG score recompute
- 2026-06-25 15:35 UTCVendor advisory
- 2026-06-25 15:35 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-17 23:56 UTCEG score recompute
- 2026-06-17 23:56 UTCVendor advisory
- 2026-06-17 23:56 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:52 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:31 UTCEG score recompute
- 2026-06-14 23:31 UTCVendor advisory
- 2026-06-14 23:31 UTCGHSA enrichment
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 11:00 UTCEG score recompute
- 2026-06-14 11:00 UTCVendor advisory
- 2026-06-14 10:59 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 02:50 UTCEG score recompute
- 2026-06-13 02:50 UTCVendor advisory
- 2026-06-13 02:50 UTCGHSA enrichment
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 14:17 UTCEG score recompute
- 2026-06-12 14:17 UTCVendor advisory
- 2026-06-12 14:17 UTCGHSA enrichment
- 2026-06-12 01:46 UTCEG score recompute
- 2026-06-12 01:46 UTCVendor advisory
- 2026-06-12 01:46 UTCGHSA enrichment
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-11 13:15 UTCEG score recompute
- 2026-06-11 13:15 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc · redhat
Same CWE
10 shownCWE-416 · CWE-362
Frequently asked(5)
What is CVE-2026-5947?
When was CVE-2026-5947 disclosed?
Is CVE-2026-5947 actively exploited?
What is the CVSS score of CVE-2026-5947?
How do I remediate CVE-2026-5947?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-5947
Is Your Infrastructure Affected by CVE-2026-5947?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.