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.7%, top 51% 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
Trending — 3 sources updated this weekElevated
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%CVSS: 7.5Exploit: Elevated riskExposed: 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)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

May 5, 2026

Last Modified

July 25, 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 9× in last 7d / 66× 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 210 total refreshes for this CVE.

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

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 July 25, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 50.7% of all scored CVEs.
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