CoreDNS gRPC/HTTPS/HTTP3 servers lack resource limits, enabling DoS via unbounded connections and oversized messages
Published 8 Jan 2026 · Updated 10 Sept 2026
Is your project on an affected github.com/coredns/coredns?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <1.14.0
- Fixed in
- 1.14.0
go get github.com/coredns/coredns@v1.14.0Details
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_
Is GHSA-527x-5wrf-22m2 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/coredns/coredns, and gives you the command that fixes it.
More advisories for github.com/coredns/coredns
- LowCVE-2026-62994CoreDNS `k8s_external` headless AXFR can emit an empty transfer batch that panics the `transfer` plugin in github.com/coredns/coredns · 19 Oct 2026
- LowCVE-2026-62994CoreDNS `k8s_external` headless AXFR can emit an empty transfer batch that panics the `transfer` plugin · 16 Oct 2026
- LowCVE-2026-86003CoreDNS DoH/DoQ/gRPC bypass UPDATE rejection enforced on UDP/TCP in github.com/coredns/coredns · 28 Sept 2026
- LowCVE-2026-82399CoreDNS: Unauthenticated memory exhaustion in custom transports in github.com/coredns/coredns · 28 Sept 2026
- HighCVE-2026-86003CoreDNS DoH/DoQ/gRPC bypass UPDATE rejection enforced on UDP/TCP · 17 Sept 2026
- HighCVE-2026-82399CoreDNS: Unauthenticated memory exhaustion in custom transports · 17 Sept 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.