CVE-2026-5950

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-05-20. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An unbounded resend loop vulnerability exists in the BIND 9 resolver state machine during bad-server handling, enabling a remote unauthenticated attacker to cause severe resource exhaustion by sending queries that trigger specific retry conditions. This issue affects BIND 9 versions 9.18.36 through 9.18.48, 9.20.8 through 9.20.22, 9.21.7 through 9.21.21, 9.18.36-S1 through 9.18.48-S1, and 9.20.9-S1 through 9.20.22-S1.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

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
Severity53% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

Published

May 20, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jun 16, 2026
Patch available.
generic

CVE-2026-5950: Unbounded resend loop in BIND 9 resolver

https://kb.isc.org/docs/cve-2026-5950
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
generic

Index of /isc/bind9/9.18.49

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

Vendor Advisories for CVE-2026-5950(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntubind9-utils (1:9.20.18-1ubuntu2.1) @ resolute2026-08-23ubuntu
redhatbind-main-9.18.49-1.hum12026-05-21redhat

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

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.18.36 up to 9.18.49-r0: fixed in 9.18.49-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.18.36 up to 9.18.49-r0: fixed in 9.18.49-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.18.36 up to 9.20.23-r0: fixed in 9.20.23-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.18.36 up to 9.20.23-r0: fixed in 9.20.23-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.18.36 up to 9.20.23-r0: fixed in 9.20.23-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.16.15-1 ... 1:9.16.50-1~deb11u5 (17 versions)
  • every version up to 1:9.16.50-1~deb11u6: fixed in 1:9.16.50-1~deb11u6
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.18.12-1 ... 1:9.18.49-1~deb12u1 (16 versions)
  • every version up to 1:9.18.49-1~deb12u2: fixed in 1:9.18.49-1~deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.20.11-4 ... 1:9.20.23-1~deb13u1~bpo12+1 (17 versions)
  • every version up to 1:9.20.23-1~deb13u1: fixed in 1:9.20.23-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.20.11-4 ... 1:9.20.23-1~deb13u1~bpo12+1 (18 versions)
  • every version up to 1:9.20.23-1: fixed in 1:9.20.23-1
—

Weakness Classification(1)

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 7× in last 7d / 23× 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 259 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-5950?
CVE-2026-5950 is a medium vulnerability published on May 20, 2026. An unbounded resend loop vulnerability exists in the BIND 9 resolver state machine during bad-server handling, enabling a remote unauthenticated attacker to cause severe resource exhaustion by sending queries that trigger specific retry conditions. This issue affects BIND 9 versions 9.18.36 through…
When was CVE-2026-5950 disclosed?
CVE-2026-5950 was first published on May 20, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5950 actively exploited?
CVE-2026-5950 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5950?
CVE-2026-5950 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-5950?
A fix for CVE-2026-5950 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-5950 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-5950?

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

Book a Demo →Browse All CVEs