CVE-2026-32936

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 86% 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: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the DNS-over-HTTPS (DoH) GET path accepts oversized dns= query parameter values and performs URL query parsing, base64 decoding, and DNS message unpacking before rejecting the request. Unlike the POST path, which applies a bounded read via http.MaxBytesReader limited to 65536 bytes, the GET path has no equivalent size validation before expensive processing. A remote, unauthenticated attacker can repeatedly send oversized DoH GET requests to force high CPU usage, large transient memory allocations, and elevated garbage-collection pressure, leading to denial of service. This issue has been fixed in version 1.14.3.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
47.6%
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

CoreDNS DoH GET oversized dns= query parameter causes pre-validation CPU and memory amplification · Advisory · coredns/coredns · GitHub

https://github.com/coredns/coredns/security/advisories/GHSA-63cw-r7xf-jmwr
generic

Release v1.14.3 · coredns/coredns · GitHub

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

Vendor Advisories for CVE-2026-32936(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/lighthouse-coredns-rhel9:17802042492026-06-10redhat

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

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

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

Frequently asked(5)

What is CVE-2026-32936?
CVE-2026-32936 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 DNS-over-HTTPS (DoH) GET path accepts oversized dns= query parameter values and performs URL query parsing, base64 decoding, and DNS message unpacking before rejecting the request. Unlike the POST path, which applies a…
When was CVE-2026-32936 disclosed?
CVE-2026-32936 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-32936 actively exploited?
CVE-2026-32936 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 47.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-32936?
CVE-2026-32936 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32936?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32936, 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-32936

Explore →

Is Your Infrastructure Affected by CVE-2026-32936?

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

Start Free Scan →Browse All CVEs