How severe is CVE-2025-68151?

No CVSS score has been assigned to CVE-2025-68151 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-68151?

CVE-2025-68151 affects the following packages: github.com/coredns/coredns (Go). Ecosystems affected: Go.

How do I fix CVE-2025-68151?

Update github.com/coredns/coredns to 1.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-68151 is resolved across your whole dependency graph.

How do I detect CVE-2025-68151 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/coredns/coredns, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-68151 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2025-68151 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-68151 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-68151?

CVE-2025-68151 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-68151?

CVE-2025-68151 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-68151 published, and has it been updated?

CVE-2025-68151 was published on January 8, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-68151 — coredns

Fix: coredns/coredns@0d8cbb1

CVE-2025-68151 is a CWE-770 vulnerability in github.com/coredns/coredns. A fix is available for github.com/coredns/coredns — see the affected versions and patch details below.

CoreDNS gRPC/HTTPS/HTTP3 servers lack resource limits, enabling DoS via unbounded connections and oversized messages

Also known asGHSA-527x-5wrf-22m2GO-2026-4289

Published

Jan 8, 2026

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-68151.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.08%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/coredns/coredns

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Multiple CoreDNS server implementations (gRPC, HTTPS, and HTTP/3) lack critical resource-limiting controls. An unauthenticated remote attacker can exhaust memory and degrade or crash the server by opening many concurrent connections, streams, or sending oversized request bodies. The issue is similar in nature to CVE-2025-47950 (QUIC DoS) but affects additional server types that do not enforce connection limits, stream limits, or message size constraints.

Impact

1. Missing connection and stream limits (gRPC / HTTPS / HTTP3)

The affected servers do not enforce reasonable upper bounds on concurrent connections or active streams. An attacker can:

Open many parallel connections
Rapidly issue requests without limit
Consume memory until the CoreDNS process becomes unresponsive or is terminated by the OOM killer

Testing demonstrates that modest resource configurations (e.g., 256 MB RAM) can be exhausted quickly. Increasing concurrency parameters in the PoCs allows attackers to scale the impact.

2. Missing message-size validation in the gRPC server

The gRPC server accepts arbitrarily large protobuf messages (default limit ~4 MB per request) without validating against DNS protocol constraints (maximum 64 KB). Sending multiple concurrent oversized messages can quickly exhaust available memory.

This vulnerability mirrors earlier hardening work in PR https://github.com/coredns/coredns/pull/7490, which applied checks for upstream proxying but left server-side request validation unprotected.

Result:

In all cases, remote unauthenticated attackers can reliably trigger memory exhaustion and cause a denial of service.

Patches

v1.14.0

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/coredns/coredns`	all versions	1.14.0`go get github.com/coredns/coredns@v1.14.0`

Affected Products

1 product · 1 configurations

Application

corednscoredns.io

< 1.14.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/coredns/coredns, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/coredns/coredns to 1.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-68151 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2025-68151 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Advanced Cluster Management for Kubernetes 2.13	`rhacm2/lighthouse-agent-rhel9:1782924920`	RHSA-2026:36873
Red Hat Advanced Cluster Management for Kubernetes 2.14	`rhacm2/lighthouse-coredns-rhel9:1780204249`	RHSA-2026:25127
Red Hat Advanced Cluster Management for Kubernetes 2.15	`rhacm2/lighthouse-coredns-rhel9:1774086225`	RHSA-2026:8151

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-68151 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works