CoreDNS is a DNS server that chains plugins. In versions prior to 1.12.2, a Denial of Service (DoS) vulnerability exists in the CoreDNS DNS-over-QUIC (DoQ) server implementation. The server previously created a new goroutine for every incoming QUIC stream without imposing any limits on the number of concurrent streams or goroutines. A remote, unauthenticated attacker could open a large number of streams, leading to uncontrolled memory consumption and eventually causing an Out Of Memory (OOM) crash — especially in containerized or memory-constrained environments. The patch in version 1.12.2 introduces two key mitigation mechanisms: max_streams, which caps the number of concurrent QUIC streams per connection with a default value of 256; and worker_pool_size, which Introduces a server-wide, bounded worker pool to process incoming streams with a default value of 1024. This eliminates the 1:1 stream-to-goroutine model and ensures that CoreDNS remains resilient under high concurrency. Some workarounds are available for those who are unable to upgrade. Disable QUIC support by removing or commenting out the quic:// block in the Corefile, use container runtime resource limits to detect and isolate excessive memory usage, and/or monitor QUIC connection patterns and alert on anomalies.
CVE-2025-47950
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.2% (67th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2025-17359 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation1.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.2%
- EPSS %ILE
- 67th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 1.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
June 6, 2025
Last Modified
August 15, 2025
Advisory Details (4)
Auto-updated Oct 27, 2026GitHub - quic-go/quic-go: A production-ready QUIC implementation in pure Go · GitHub
https://github.com/quic-go/quic-goDoQ Memory Exhaustion via Stream Amplification · Advisory · coredns/coredns · GitHub
https://github.com/coredns/coredns/security/advisories/GHSA-cvx7-x8pj-x2gwcommit efaed02c6a48 (coredns/coredns)
Fix landed in coredns/coredns commit efaed02c6a48 — awaiting tagged release
https://github.com/coredns/coredns/commit/efaed02c6a480ec147b1f799aab7cf815b17dfe1Vendor Advisories for CVE-2025-47950(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:36873Red Hat Product SecurityHigh
Red Hat Security Advisory: Submariner v0.20 security fixes and container updates
- RHSA-2025:21892Red Hat Product SecurityMedium
Red Hat Security Advisory: Submariner v0.21 security fixes and container updates
- RHSA-2025:17128Red Hat Product SecurityMedium
Red Hat Security Advisory: Submariner v0.20.2 security fixes and container updates
- CVE-2025-47950Microsoft Security Response Center (MSRC)High
CoreDNS Vulnerable to DoQ Memory Exhaustion via Stream Amplification
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | rhacm2/lighthouse-coredns-rhel9:1782924937 | 2026-07-08 | redhat |
| redhat | rhacm2/lighthouse-coredns-rhel9:v0.21-1762794442 | 2025-11-20 | redhat |
| redhat | rhacm2/lighthouse-coredns-rhel9:v0.20.2-1759168533 | 2025-10-01 | redhat |
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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/coredns/coredns | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 39× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 95 of 201 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-29 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-28 16:30 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-27 12:32 UTCEG score recompute
- 2026-10-27 12:32 UTCVendor advisory
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-25 16:22 UTCEG score recompute
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-18 15:01 UTCVendor advisory
- 2026-10-18 05:30 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-16 16:38 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-13 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-12 17:01 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
Show 70 moreShow fewer
- 2026-10-11 20:35 UTCEG score recompute
- 2026-10-11 18:46 UTCEG score recompute
- 2026-10-11 15:22 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 1.2% · 67th percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-10-08 17:10 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-10-02 11:41 UTCOSV refresh
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-27 13:45 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-26 00:25 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-21 21:06 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-20 20:15 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-17 19:29 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-15 03:09 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-13 10:24 UTCOSV refresh
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-11 09:36 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-08 21:59 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-07 16:00 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-05 15:28 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-01 04:38 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-27 14:24 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-25 11:11 UTCOSV refresh
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-24 09:22 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-20 22:54 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-18 13:47 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-17 13:46 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-11 13:41 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-10 23:59 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-09 03:27 UTCOSV refresh
- 2026-08-08 16:36 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-06 13:46 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-05 19:16 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-04 15:09 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-04 10:37 UTCEPSS rescoreEPSS 1.2% · 64th percentile
- 2026-08-03 10:35 UTCEPSS rescoreEPSS 1.2% · 64th percentile
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownGo:github.com/coredns/coredns
Same vendor
10 shownredhat:RHSA-2025:21892 · redhat:RHSA-2026:36873
Frequently asked(5)
What is CVE-2025-47950?
When was the CVE record for CVE-2025-47950 published?
Is CVE-2025-47950 actively exploited?
What is the CVSS score of CVE-2025-47950?
How do I remediate CVE-2025-47950?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-47950
Is Your Infrastructure Affected by CVE-2025-47950?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.