CVE-2025-68151: CoreDNS gRPC/HTTPS/HTTP3 servers lack resource limits, enabling DoS via unbounded connections and oversized messages
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.
Published Jan 8, 2026
Affected packages
github.com/coredns/coredns
- Ecosystem
- Go
- Affected
- < 1.14.0
- Fixed in
- 1.14.0
- Check
go list -m github.com/coredns/coredns
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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_
Credited to thevilledev.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-62994
CoreDNS `k8s_external` headless AXFR can emit an empty transfer batch that panics the `transfer` plugin
low3.7Oct 16, 2026CVE-2026-82399
CoreDNS: Unauthenticated memory exhaustion in custom transports
high7.5Sep 17, 2026CVE-2026-86003
CoreDNS DoH/DoQ/gRPC bypass UPDATE rejection enforced on UDP/TCP
high7.5Sep 17, 2026CVE-2026-32934
CoreDNS' DoQ worker pool does not bound stream backlog
high7.5Apr 28, 2026CVE-2026-32936
CoreDNS DoH GET oversized dns= query parameter causes pre-validation CPU and memory amplification
high7.5Apr 28, 2026CVE-2026-33190
CoreDNS has TSIG authentication bypass on DoT, DoH, DoH3, DoQ, and gRPC
high7.5Apr 28, 2026
