CVE-2026-33489

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the transfer plugin can select the wrong ACL stanza when both a parent zone and a more-specific subzone are configured. The longestMatch() function in plugin/transfer/transfer.go uses a lexicographic string comparison instead of an actual longest-suffix match to select the winning zone. As a result, a permissive parent-zone transfer rule can override a restrictive subzone rule depending on zone name ordering (e.g., "example.org." > "a.example.org." lexicographically). This allows an unauthorized remote client to perform AXFR/IXFR for the subzone and retrieve its full zone contents. This issue has been fixed in version 1.14.3.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
31.0%
KEV
Not listed

Published

May 5, 2026

Last Modified

May 8, 2026

Advisory Details (2)

Auto-updated May 5, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Transfer stanza selection uses lexicographic compare (subzone ACL bypass) · Advisory · coredns/coredns · GitHub

https://github.com/coredns/coredns/security/advisories/GHSA-h8mm-c463-wjq3
generic

Release v1.14.3 · coredns/coredns · GitHub

https://github.com/coredns/coredns/releases/tag/v1.14.3

Vendor Advisories for CVE-2026-33489(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/coredns/coredns—1.14.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 41× 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 140 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33489?
CVE-2026-33489 is a high vulnerability published on May 5, 2026. CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the transfer plugin can select the wrong ACL stanza when both a parent zone and a more-specific subzone are configured. The longestMatch() function in plugin/transfer/transfer.go uses a lexicographic string comparison instead…
When was CVE-2026-33489 disclosed?
CVE-2026-33489 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33489 actively exploited?
CVE-2026-33489 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33489?
CVE-2026-33489 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33489?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33489, 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-33489

Explore →

Is Your Infrastructure Affected by CVE-2026-33489?

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

Start Free Scan →Browse All CVEs