CVE-2026-3039

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

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.5(medium)
EPSS
60.6%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 15, 2026

Advisory Details (4)

Auto-updated Jun 6, 2026
No patch confirmed yet.
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(3)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntubind9-utils (1:9.20.18-1ubuntu2.1) @ resolute2026-06-29ubuntu
redhatbind-32:9.11.36-16.el8_10.82026-06-08redhat
redhatbind-32:9.18.33-15.el10_2.22026-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
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.

Weakness Classification(2)

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

Additional Vendor Advisories

(6)

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 / 49× 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 167 total refreshes for this CVE.

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

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 in the National Vulnerability Database on May 20, 2026, with the most recent update on July 15, 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 60.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-3039?
CVE-2026-3039 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-3039?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3039, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs