CVE-2026-32934

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, 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
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 DNS-over-QUIC (DoQ) server can be driven into unbounded goroutine and memory growth by a remote client that opens many QUIC streams and sends only 1 byte per stream. When the worker pool is full, CoreDNS still spawns a goroutine per accepted stream to wait for a worker token. Additionally, active workers block indefinitely in io.ReadFull() with no per-stream read deadline, allowing an attacker to pin all workers by sending a single byte so the read blocks waiting for the second byte of the DoQ length prefix. This enables an unauthenticated remote attacker to cause memory exhaustion and OOM-kill. This issue has been fixed in version 1.14.3. No known workarounds exist.

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

DoQ worker pool does not bound stream backlog · Advisory · coredns/coredns · GitHub

https://github.com/coredns/coredns/security/advisories/GHSA-2wpx-qpw2-g5h5
generic

Release v1.14.3 · coredns/coredns · GitHub

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

Vendor Advisories for CVE-2026-32934(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 9× in last 7d / 47× 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 145 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-32934?
CVE-2026-32934 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-QUIC (DoQ) server can be driven into unbounded goroutine and memory growth by a remote client that opens many QUIC streams and sends only 1 byte per stream. When the worker pool is full, CoreDNS still spawns a…
When was CVE-2026-32934 disclosed?
CVE-2026-32934 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-32934 actively exploited?
CVE-2026-32934 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-32934?
CVE-2026-32934 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32934?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32934, 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-32934

Explore →

Is Your Infrastructure Affected by CVE-2026-32934?

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

Start Free Scan →Browse All CVEs