CVE-2026-62299 json
CoreDNS: rewrite-plugin EDNS0 response-revert nil-pointer panic (remote DoS) when a downstream plugin returns a response with no OPT record
published 2026-07-16 3 mo ago modified 2026-07-22 3 mo ago also EUVD-2026-45020
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
CoreDNS is a DNS server written in Go. Prior to 1.14.5, the CoreDNS rewrite plugin supports edns0 rewrite rules with an optional revert flag, and two response rules, edns0SetResponseRule and edns0ReplaceResponseRule[T] in plugin/rewrite/edns0.go, call res.IsEdns0() and immediately dereference the returned *dns.OPT without a nil check when a downstream plugin returns a response with no OPT record. A remote, unauthenticated client can send a single ordinary DNS query matching a rewrite edns0 <local|nsid|subnet> <set|append|replace> ... revert rule, causing ResponseReverter in plugin/rewrite/reverter.go to panic, return SERVFAIL, and degrade availability, or crash the CoreDNS process if the debug directive disables recovery. This issue is fixed in version 1.14.5.
Patch / fix
- coredns.io coredns 1.14.5
- github.com/coredns/coredns@fc447d0 commit
- github.com/coredns/coredns#8190 pull request
- github.com/coredns/coredns/releases/tag/v1.14.5 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-62299 updated cvss 5.3
github.com/coredns/coredns: CoreDNS: Denial of Service via specially crafted DNS query
-
Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/lighthouse-agent-rhel9, rhacm2/lighthouse-coredns-rhel9 Red Hat Connectivity Link 1 rhcl-1/coredns-rhel9 Red Hat OpenShift Container Platform 4 openshift4/ose-coredns, openshift4/ose-coredns-rhel9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/coredns/coredns/security/advisories/GHSA-9pmm-cxww-rrr7 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected products
- coredns coredns
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
github.com
/coredns/coredns/pull/8190
issue-tracking, patch
-
github.com
/coredns/coredns/commit/fc447d0658b093edc8cd29a6b171216a44a644c2
patch
-
github.com
/coredns/coredns/security/advisories/GHSA-9pmm-cxww-rrr7
exploit, third-party-advisory
-
github.com
/coredns/coredns/releases/tag/v1.14.5
release-notes
Sources
- CVE List CVE-2026-62299
- NVD CVE-2026-62299
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.