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.
CVE-2026-32934
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 39%
- KEV
- Not listed
Published
May 5, 2026
Last Modified
July 25, 2026
Advisory Details (2)
Auto-updated May 5, 2026DoQ worker pool does not bound stream backlog · Advisory · coredns/coredns · GitHub
https://github.com/coredns/coredns/security/advisories/GHSA-2wpx-qpw2-g5h5Release v1.14.3 · coredns/coredns · GitHub
https://github.com/coredns/coredns/releases/tag/v1.14.3Vendor 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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| 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 / 55× 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 216 total refreshes for this CVE.
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 20:43 UTCEG score recompute
- 2026-08-23 20:43 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 13:01 UTCEG score recompute
- 2026-08-17 13:01 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:58 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-16 04:58 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 02:04 UTCEG score recompute
- 2026-08-15 02:04 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 14:49 UTCVendor advisory
- 2026-08-14 03:34 UTCEG score recompute
- 2026-08-14 03:34 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 17:11 UTCEG score recompute
- 2026-08-12 17:11 UTCVendor advisory
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 16:02 UTCEG score recompute
- 2026-08-11 16:02 UTCVendor advisory
- 2026-08-11 01:36 UTCEG score recompute
- 2026-08-11 01:36 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 01:10 UTCVendor advisory
- 2026-08-09 13:55 UTCEG score recompute
- 2026-08-09 13:55 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 02:39 UTCEG score recompute
- 2026-08-09 02:39 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 22:33 UTCEG score recompute
- 2026-08-07 11:18 UTCVendor advisory
- 2026-08-06 20:55 UTCEG score recompute
- 2026-08-06 20:55 UTCVendor advisory
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 09:40 UTCVendor advisory
- 2026-08-05 22:25 UTCEG score recompute
- 2026-08-05 22:25 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 19:56 UTCEG score recompute
- 2026-08-03 19:56 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 04:01 UTCVendor advisory
- 2026-08-02 16:30 UTCVendor advisory
- 2026-08-02 05:15 UTCEG score recompute
- 2026-08-02 05:15 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 08:31 UTCEG score recompute
- 2026-07-26 08:31 UTCVendor advisory
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:09 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 22:32 UTCOSV refresh
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-32934?
When was CVE-2026-32934 disclosed?
Is CVE-2026-32934 actively exploited?
What is the CVSS score of CVE-2026-32934?
How do I remediate CVE-2026-32934?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32934
Is Your Infrastructure Affected by CVE-2026-32934?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.