CVE-2026-3039

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessive memory consumption when receiving and processing maliciously-constructed packets. Typically these servers will be found in Active Directory integrated DNS deployments and/or Kerberos-secured DNS environments. This issue affects BIND 9 versions 9.0.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.9.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
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
1.0%
EPSS %ILE
63rd
KEV
Not listed

Published

May 20, 2026

Last Modified

September 17, 2026

Advisory Details (4)

Auto-updated Jun 6, 2026
Patch available.
generic

CVE-2026-3039: BIND 9 server memory exhaustion during GSS-API TKEY negotiation

https://kb.isc.org/docs/cve-2026-3039
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-3039(15)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhcos-418.94.202609031320-02026-09-17redhat
ubuntudnsutils (1:9.18.39-0ubuntu0.22.04.4) @ jammy2026-09-17ubuntu
ubuntulwresd (1:9.10.3.dfsg.P4-8ubuntu1.19+esm10) @ xenial2026-09-17ubuntu
redhatrhcos-416.94.202609011112-02026-09-10redhat
redhatbind-32:9.11.4-26.P2.el7_9.212026-08-26redhat
redhatbind-32:9.16.23-18.el9_4.122026-08-19redhat
redhatbind-32:9.16.23-31.el9_6.42026-08-17redhat
redhatbind-32:9.11.36-16.el8_10.82026-06-08redhat
redhatbind9.18-32:9.18.29-14.el9_8.22026-06-08redhat
redhatbind-32:9.16.23-40.el9_8.22026-06-08redhat
redhatbind-32:9.18.33-15.el10_2.22026-06-08redhat
redhatbind9.16-32:9.16.23-0.22.el8_10.62026-06-04redhat
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.0.0 up to 9.18.49-r0: fixed in 9.18.49-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.49-r0: fixed in 9.18.49-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.20.23-r0: fixed in 9.20.23-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.20.23-r0: fixed in 9.20.23-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 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(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

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 8× in last 7d / 38× 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 354 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-3039?
CVE-2026-3039 is a high vulnerability published on May 20, 2026. BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessive memory consumption when receiving and processing maliciously-constructed packets. Typically these servers will be found in Active Directory integrated DNS deployments and/or…
When was CVE-2026-3039 disclosed?
CVE-2026-3039 was first published on May 20, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3039 actively exploited?
CVE-2026-3039 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3039?
CVE-2026-3039 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-3039?
A fix for CVE-2026-3039 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-3039 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-3039

Explore →

Is Your Infrastructure Affected by CVE-2026-3039?

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

Book a Demo →Browse All CVEs