CoreDNS is a DNS server written in Go. From 1.9.4 until 1.14.5, a network DNS client allowed to request AXFR for a CoreDNS zone can trigger a panic when CoreDNS is configured with k8s_external headless-service zone transfers and Kubernetes contains a headless service endpoint with no declared ports; plugin/kubernetes/object/endpoint.go creates Port: -1, plugin/k8s_external/msg_to_dns.go skips that service, plugin/k8s_external/transfer.go sends an empty []dns.RR batch, and plugin/transfer/transfer.go indexes records[0] without checking the batch is non-empty. This issue is fixed in version 1.14.5.
CVE-2026-62994
LOWPre-NVD 3.73.7—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
3.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.7Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(medium)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity37% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 19.6%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 22, 2026
References (5)
- security-advisories@githubhttps://github.com/coredns/coredns/commit/ab318db7b4a3a19273852ed627f54888198c8efb
- security-advisories@githubhttps://github.com/coredns/coredns/pull/8207
- security-advisories@githubhttps://github.com/coredns/coredns/releases/tag/v1.14.5
- security-advisories@githubhttps://github.com/coredns/coredns/security/advisories/GHSA-74w3-63xv-x9mv
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/coredns/coredns/security/advisories/GHSA-74w3-63xv-x9mv
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:34 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 14:02 UTCEG score recompute
- 2026-07-17 11:34 UTCEG score recompute
- 2026-07-16 19:45 UTCEG score recompute
- 2026-07-16 19:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-755 · CWE-248
- CVE-2009-5043EG 9.8CRITICAL
- CVE-2019-17195EG 9.8EPSS 95%CRITICAL
- CVE-2019-14431EG 9.8CRITICAL
- CVE-2019-12815EG 9.8EPSS 99%CRITICAL
- CVE-2018-11466EG 9.8CRITICAL
- CVE-2018-19991EG 9.8CRITICAL
- CVE-2017-2877EG 9.8CRITICAL
- CVE-2017-5638EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2018-0155NVD 8.6EG 9.0 KEVEPSS 94%HIGH
- CVE-2019-14287EG 8.9EPSS 99%HIGH
Frequently asked(5)
What is CVE-2026-62994?
CVE-2026-62994 is a low vulnerability published on July 16, 2026. CoreDNS is a DNS server written in Go. From 1.9.4 until 1.14.5, a network DNS client allowed to request AXFR for a CoreDNS zone can trigger a panic when CoreDNS is configured with k8sexternal headless-service zone transfers and Kubernetes contains a headless service endpoint with no declared ports;…
When was CVE-2026-62994 disclosed?
CVE-2026-62994 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62994 actively exploited?
CVE-2026-62994 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-62994?
CVE-2026-62994 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-62994?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62994, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62994
Is Your Infrastructure Affected by CVE-2026-62994?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.