CVE-2026-62299

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-45020 (ENISA EUVD)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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 ... 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.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 16, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jul 17, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

rewrite-plugin EDNS0 response-revert nil-pointer panic (remote DoS) when a downstream plugin returns a response with no OPT record · Advisory · coredns/coredns · GitHub

https://github.com/coredns/coredns/security/advisories/GHSA-9pmm-cxww-rrr7
GitHub release Patch Available

v1.14.5

Patch available: coredns/coredns v1.14.5

https://github.com/coredns/coredns/releases/tag/v1.14.5
GitHub pull request

plugin/rewrite: Fix nil-pointer panic in EDNS0 response reversion with no OPT record

Fix merged in coredns/coredns PR #8190 on 2026-06-23 — awaiting tagged release

https://github.com/coredns/coredns/pull/8190
GitHub commit

commit fc447d0658b0 (coredns/coredns)

Fix landed in coredns/coredns commit fc447d0658b0 — awaiting tagged release

https://github.com/coredns/coredns/commit/fc447d0658b093edc8cd29a6b171216a44a644c2

Vendor Advisories for CVE-2026-62299(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 188 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 88 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-10-25 14:14 UTCEG score recompute
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-22 19:53 UTCEG score recompute
  7. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-18 03:24 UTCEG score recompute
  13. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-12 15:49 UTCEG score recompute
  20. 2026-10-11 19:34 UTCEG score recompute
  21. 2026-10-11 16:49 UTCEG score recompute
  22. 2026-10-11 14:11 UTCEG score recompute
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 75 more
  1. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-01 11:22 UTCEG score recompute
  10. 2026-10-01 11:22 UTCVendor advisory
  11. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-09-28 08:16 UTCEG score recompute
  14. 2026-09-28 08:16 UTCVendor advisory
  15. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-09-24 06:58 UTCEG score recompute
  17. 2026-09-24 06:58 UTCVendor advisory
  18. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-09-23 03:01 UTCEG score recompute
  20. 2026-09-23 03:01 UTCVendor advisory
  21. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-09-18 09:56 UTCEG score recompute
  24. 2026-09-18 09:56 UTCVendor advisory
  25. 2026-09-17 10:29 UTCEG score recompute
  26. 2026-09-17 10:29 UTCVendor advisory
  27. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  28. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  29. 2026-09-14 06:17 UTCEG score recompute
  30. 2026-09-14 06:17 UTCVendor advisory
  31. 2026-09-13 07:07 UTCEG score recompute
  32. 2026-09-13 07:07 UTCVendor advisory
  33. 2026-09-11 21:39 UTCEG score recompute
  34. 2026-09-11 21:39 UTCVendor advisory
  35. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  37. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-09-08 00:26 UTCEG score recompute
  39. 2026-09-08 00:26 UTCVendor advisory
  40. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  41. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-09-05 20:33 UTCEG score recompute
  43. 2026-09-05 20:33 UTCVendor advisory
  44. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  45. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  46. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  47. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  48. 2026-08-31 02:41 UTCEG score recompute
  49. 2026-08-31 02:41 UTCVendor advisory
  50. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  51. 2026-08-30 03:30 UTCEG score recompute
  52. 2026-08-30 03:30 UTCVendor advisory
  53. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  54. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  55. 2026-08-27 21:56 UTCEG score recompute
  56. 2026-08-27 21:56 UTCVendor advisory
  57. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  58. 2026-08-26 22:47 UTCEG score recompute
  59. 2026-08-26 22:47 UTCVendor advisory
  60. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  61. 2026-08-25 18:58 UTCEG score recompute
  62. 2026-08-25 18:58 UTCVendor advisory
  63. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  64. 2026-08-24 19:49 UTCEG score recompute
  65. 2026-08-24 19:49 UTCVendor advisory
  66. 2026-08-23 20:39 UTCEG score recompute
  67. 2026-08-23 20:39 UTCVendor advisory
  68. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  69. 2026-08-22 21:30 UTCEG score recompute
  70. 2026-08-22 21:30 UTCVendor advisory
  71. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  72. 2026-08-20 23:02 UTCEG score recompute
  73. 2026-08-20 23:02 UTCVendor advisory
  74. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  75. 2026-08-19 23:52 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-62299?
CVE-2026-62299 is a medium-severity vulnerability; its CVE record was published on July 16, 2026. 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…
When was the CVE record for CVE-2026-62299 published?
The CVE record for CVE-2026-62299 was published on July 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-62299 actively exploited?
CVE-2026-62299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62299?
CVE-2026-62299 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62299?
A fix for CVE-2026-62299 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62299 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62299

Explore →

Is Your Infrastructure Affected by CVE-2026-62299?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.