CVE-2026-3592

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
Trending — 4 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

BIND resolvers are vulnerable to an amplified resource consumption/exhaustion attack. If a victim resolver makes a query to a specially crafted zone, the resolver will consume disproportionate resources. 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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 24, 2026

Advisory Details (4)

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

CVE-2026-3592: Amplification vulnerabilities via self-pointed glue records

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

Patch Availability(2)

Vendor / EcosystemFixed in / 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 rangeFixed inDependents
bind9.18.49-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
bind9.18.49-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
bind9.20.23-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
bind9.20.23-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
bind9.20.23-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bind91:9.16.15-1 ... 1:9.16.50-1~deb11u5 (17 versions)1:9.16.50-1~deb11u6
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bind91:9.18.12-1 ... 1:9.18.49-1~deb12u1 (16 versions)1:9.18.49-1~deb12u2
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(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 14× in last 7d / 80× 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 222 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-3592?
CVE-2026-3592 is a medium vulnerability published on May 20, 2026. BIND resolvers are vulnerable to an amplified resource consumption/exhaustion attack. If a victim resolver makes a query to a specially crafted zone, the resolver will consume disproportionate resources. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.48, 9.20.0…
When was CVE-2026-3592 disclosed?
CVE-2026-3592 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3592 actively exploited?
CVE-2026-3592 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.6% of all scored CVEs.
What is the CVSS score of CVE-2026-3592?
CVE-2026-3592 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-3592?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3592, 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-3592

Explore →

Is Your Infrastructure Affected by CVE-2026-3592?

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