Skip to main content
No exploitation reportedFix available

CVE-2025-47950

No exploitation reported by the sources we read.

  • Published2025-06-06
  • Fixed in1.12.2
  • WeaknessCWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2025-06-0618:15CVE publishedNVD

Versions per branch

NVD · OSV
Coredns.io coredns
BranchAffectedFixed in
1.12< 1.12.21.12.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • coredns
    Affected
    • = < 1.12.2no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-06-06

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • cloudflaredWolfiall versions · fixed in 0
  • cloudflaredChainguardall versions · fixed in 0
  • corednsAzure Linux:3all versions · fixed in 1.11.4-7
  • corednsAzure Linux:2all versions · fixed in 1.11.1-19
  • coredns-1.11MinimOSall versions · no fixed version listedand 8 other packages
  • eks-distro-coredns-1.29Chainguardall versions · fixed in 1.29.53-r1and 1 other package
  • eks-distro-coredns-1.30Chainguardall versions · fixed in 1.30.46-r1and 1 other package
  • eks-distro-coredns-1.31Chainguardall versions · fixed in 1.31.35-r1and 1 other package

15 more package ranges on OSV.dev

Vendor advisories

  • CVE-2025-47950 Red Hat Product Security20 products fixed

    coredns: CoreDNS Vulnerable to DoQ Memory Exhaustion via Stream Amplification

  • RHSA-2026:36873 Red Hat Product Security8 products fixed

    Red Hat Security Advisory: Submariner v0.20 security fixes and container updates

  • RHSA-2025:21892 Red Hat Product Security8 products fixed

    Red Hat Security Advisory: Submariner v0.21 security fixes and container updates

  • RHSA-2025:17128 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: Submariner v0.20.2 security fixes and container updates

Full record on NVD

Fix

  1. Update Coredns.io coredns to 1.12.2
  2. Vendor fix Red Hat Product Security RHSA-2026:36873 · 8 productsFor release note details, see the upstream Submariner release notes: https://submariner.io/community/releases/ Downstream-specific issues resolved: * ACM-17819 * ACM-21727 * ACM-21731 * ACM-24786 * ACM-25148 * ACM-25152 * ACM-25169 * ACM-29510 * ACM-29564 * ACM-29565 * ACM-29574 * ACM-29584 * ACM…
  3. Vendor fix Red Hat Product Security RHSA-2025:21892 · 8 productsFor release note details, see the upstream Submariner release notes: https://submariner.io/community/releases/ Downstream-specific issues resolved: * ACM-18625 For more details, see the Red Hat Advanced Cluster Management for Kubernetes documentation: https://docs.redhat.com/documentation/en-u…
  4. Vendor fix Red Hat Product Security RHSA-2025:17128 · 4 productsFor release note details, see the upstream Submariner release notes: https://submariner.io/community/releases/ For more details, see the Red Hat Advanced Cluster Management for Kubernetes documentation: https://docs.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernete…
  5. Workaround from the vendor Red Hat Product Security RHSA-2026:36873 · 33 productsUsers unable to upgrade should manually disable the QUIC protocol support.

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2025-06-06
  • CNACVSS 3.17.5known since 2026-10-23
  • CNAweakness (CWE)CWE-770known since 2026-10-23
  • FIRST EPSSEPSS score1.2 %2026-11-18
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2025-06-06

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2025-06-06
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-cvx7-x8pj-x2gw

Frequently asked questions

What is CVE-2025-47950?

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.

Is CVE-2025-47950 actively exploited?

Active exploitation of CVE-2025-47950 has not been confirmed. Its EPSS score was 1.2% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-47950?

CVE-2025-47950 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running coredns/coredns? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record