Skip to main content
VulnerabilityPublished

CVE-2026-82399: CoreDNS · Unauthenticated memory exhaustion in custom transports

Affects github.com/coredns/corednsSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.14.7 soon.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.14.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade github.com/coredns/coredns to 1.14.7.

Affected software

ProductAffectedFixed in
Gogithub.com/coredns/corednsAffected
  • <1.14.7
Fixed in
  • 1.14.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for CoreDNS that fixes this issue by applying proper validation of DNS section counts before unpacking requests in the affected custom transports. Users should upgrade to CoreDNS version 1.14.7 or later. Until patched, mitigating controls at the network level (such as rate limiting or filtering malformed DNS-over-HTTPS/QUIC/gRPC requests) may help reduce exposure, but the root cause is fixed only by applying the official update.

Description

CoreDNS versions prior to 1.14.7 contain a vulnerability in their custom transport implementations for DNS-over-HTTPS (DoH/DoH3), DNS-over-QUIC (DoQ), and DNS-over-gRPC. An unauthenticated attacker can craft DNS requests with maliciously large section counts using DNS name compression, causing excessive memory allocation during request unpacking. This can lead to memory exhaustion and termination of the CoreDNS process. The issue arises because CoreDNS bypasses early validation of DNS section counts that is present in the underlying miekg/dns UDP and TCP server implementations. A patch is available that applies proper validation before unpacking requests to prevent this memory exhaustion.

References

Community reviews

Loading reviews…