CVE-2026-62299

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% 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
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.3(medium)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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 computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jul 17, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

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_pr

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 / 59× 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.

Showing the most recent 100 of 129 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-62299?
CVE-2026-62299 is a medium vulnerability 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 CVE-2026-62299 disclosed?
CVE-2026-62299 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-62299 actively exploited?
CVE-2026-62299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.4% of all scored CVEs.
What is the CVSS score of CVE-2026-62299?
CVE-2026-62299 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-62299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62299, 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-62299

Explore →

Is Your Infrastructure Affected by CVE-2026-62299?

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

Start Free Scan →Browse All CVEs