CVE-2026-5947

HIGHNVD 5.97.5▲
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. NVD baseline CVSS 5.9; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
70%
KEV
Not listed

Published

May 20, 2026

Last Modified

September 1, 2026

Advisory Details (3)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

CVE-2026-5947: SIG(0) validation during query flood may lead to undefined behavior

https://kb.isc.org/docs/cve-2026-5947
generic

Index of /isc/bind9/9.21.22

https://downloads.isc.org/isc/bind9/9.21.22
generic

Index of /isc/bind9/9.20.23

https://downloads.isc.org/isc/bind9/9.20.23

Vendor 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.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntubind9-utils (1:9.20.18-1ubuntu2.1) @ resolute2026-08-24ubuntu
redhatbind-main-9.18.48-1.1.hum12026-04-10redhat

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.

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
bind—9.18.49-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
bind—9.18.49-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
bind—9.20.23-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
bind—9.20.23-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
bind—9.20.23-r0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bind91:9.20.11-4 ... 1:9.20.23-1~deb13u1~bpo12+1 (17 versions)1:9.20.23-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bind91:9.20.11-4 ... 1:9.20.23-1~deb13u1~bpo12+1 (18 versions)1:9.20.23-1—

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 9× in last 7d / 88× 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 293 total refreshes for this CVE.

  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 12:21 UTCEG score recompute
  5. 2026-09-01 12:21 UTCVendor advisory
  6. 2026-09-01 12:21 UTCGHSA enrichment
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-28 21:42 UTCEPSS rescore
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-26 14:46 UTCEPSS rescore
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-24 13:29 UTCVendor advisory
  15. 2026-08-24 13:29 UTCGHSA enrichment
  16. 2026-08-24 12:25 UTCEG score recompute
  17. 2026-08-24 12:25 UTCVendor advisory
  18. 2026-08-24 12:25 UTCGHSA enrichment
  19. 2026-08-23 16:55 UTCEG score recompute
  20. 2026-08-23 16:55 UTCVendor advisory
  21. 2026-08-23 16:55 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 22:55 UTCEG score recompute
  25. 2026-08-21 22:55 UTCVendor advisory
Show 75 more
  1. 2026-08-21 22:55 UTCGHSA enrichment
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-20 18:55 UTCEG score recompute
  4. 2026-08-20 18:55 UTCVendor advisory
  5. 2026-08-20 18:55 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 09:53 UTCVendor advisory
  10. 2026-08-17 09:53 UTCGHSA enrichment
  11. 2026-08-16 16:54 UTCEG score recompute
  12. 2026-08-16 16:54 UTCVendor advisory
  13. 2026-08-16 16:54 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 03:30 UTCEG score recompute
  16. 2026-08-16 03:30 UTCVendor advisory
  17. 2026-08-16 03:30 UTCGHSA enrichment
  18. 2026-08-15 03:17 UTCEG score recompute
  19. 2026-08-15 03:17 UTCVendor advisory
  20. 2026-08-15 03:17 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 14:32 UTCVendor advisory
  23. 2026-08-14 14:32 UTCGHSA enrichment
  24. 2026-08-14 02:01 UTCEG score recompute
  25. 2026-08-14 02:01 UTCVendor advisory
  26. 2026-08-14 02:01 UTCGHSA enrichment
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-13 03:23 UTCVendor advisory
  29. 2026-08-13 03:23 UTCGHSA enrichment
  30. 2026-08-12 14:52 UTCEG score recompute
  31. 2026-08-12 14:52 UTCVendor advisory
  32. 2026-08-12 14:52 UTCGHSA enrichment
  33. 2026-08-12 13:51 UTCEPSS rescore
  34. 2026-08-12 02:22 UTCVendor advisory
  35. 2026-08-12 02:22 UTCGHSA enrichment
  36. 2026-08-11 13:51 UTCEG score recompute
  37. 2026-08-11 13:51 UTCVendor advisory
  38. 2026-08-11 13:51 UTCGHSA enrichment
  39. 2026-08-11 00:35 UTCEG score recompute
  40. 2026-08-11 00:35 UTCVendor advisory
  41. 2026-08-11 00:35 UTCGHSA enrichment
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-10 02:33 UTCVendor advisory
  44. 2026-08-10 02:33 UTCGHSA enrichment
  45. 2026-08-09 14:02 UTCEG score recompute
  46. 2026-08-09 14:02 UTCVendor advisory
  47. 2026-08-09 14:02 UTCGHSA enrichment
  48. 2026-08-09 13:46 UTCEPSS rescore
  49. 2026-08-09 01:32 UTCEG score recompute
  50. 2026-08-09 01:32 UTCVendor advisory
  51. 2026-08-09 01:32 UTCGHSA enrichment
  52. 2026-08-08 16:37 UTCEPSS rescore
  53. 2026-08-08 02:01 UTCEG score recompute
  54. 2026-08-08 02:01 UTCVendor advisory
  55. 2026-08-08 02:01 UTCGHSA enrichment
  56. 2026-08-07 13:30 UTCVendor advisory
  57. 2026-08-07 13:30 UTCGHSA enrichment
  58. 2026-08-07 01:00 UTCEG score recompute
  59. 2026-08-07 01:00 UTCVendor advisory
  60. 2026-08-07 01:00 UTCGHSA enrichment
  61. 2026-08-06 13:47 UTCEPSS rescore
  62. 2026-08-06 09:52 UTCVendor advisory
  63. 2026-08-06 09:51 UTCGHSA enrichment
  64. 2026-08-05 21:17 UTCEG score recompute
  65. 2026-08-05 21:17 UTCVendor advisory
  66. 2026-08-05 21:17 UTCGHSA enrichment
  67. 2026-08-05 19:17 UTCEPSS rescore
  68. 2026-08-04 15:10 UTCEPSS rescore
  69. 2026-08-04 10:39 UTCEPSS rescore
  70. 2026-08-04 05:26 UTCVendor advisory
  71. 2026-08-04 05:26 UTCGHSA enrichment
  72. 2026-08-03 16:54 UTCEG score recompute
  73. 2026-08-03 16:54 UTCVendor advisory
  74. 2026-08-03 16:54 UTCGHSA enrichment
  75. 2026-08-03 10:36 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-5947?
CVE-2026-5947 is a high vulnerability published on May 20, 2026. 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…
When was CVE-2026-5947 disclosed?
CVE-2026-5947 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5947 actively exploited?
CVE-2026-5947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 29.6% of all scored CVEs.
What is the CVSS score of CVE-2026-5947?
CVE-2026-5947 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.5.
How do I remediate CVE-2026-5947?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5947, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-5947

Explore →

Is Your Infrastructure Affected by CVE-2026-5947?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs