CVE-2026-62309

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 51% 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 — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

CoreDNS is a DNS server written in Go. Prior to 1.14.4, a single 28-byte UDP datagram can crash the CoreDNS process when the proxyproto plugin is enabled because plugin/pkg/proxyproto/proxyproto.go PacketConn.ReadFrom handles a PROXY v2 header with non-UDP transport such as family byte 0x11, reassigns addr from a nil readFrom result after parseProxyProtocol errors, and calls addr.String() in the warning log before ServeDNS recovery applies. This issue is fixed in version 1.14.4.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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 computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jul 16, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

proxyproto plugin panics on PPv2 datagram with non-UDP transport — single 28-byte packet remote DoS · Advisory · coredns/coredns · GitHub

https://github.com/coredns/coredns/security/advisories/GHSA-9rvv-m5g5-wc8r
github_release Patch Available

v1.14.4

Patch available: coredns/coredns v1.14.4

https://github.com/coredns/coredns/releases/tag/v1.14.4
github_pr

plugin/proxyproto: Prevent nil pointer dereference when dropping malformed PROXY packets

Fix merged in coredns/coredns PR #8154 on 2026-06-08 — awaiting tagged release

https://github.com/coredns/coredns/pull/8154
github_commit

commit 60a439dd4feb (coredns/coredns)

Fix landed in coredns/coredns commit 60a439dd4feb — awaiting tagged release

https://github.com/coredns/coredns/commit/60a439dd4febfcd78e3779e952fe3fbf3c16bb1f

Vendor Advisories for CVE-2026-62309(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/lighthouse-coredns-rhel9:17880239402026-09-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 49× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-62309?
CVE-2026-62309 is a high vulnerability published on July 16, 2026. CoreDNS is a DNS server written in Go. Prior to 1.14.4, a single 28-byte UDP datagram can crash the CoreDNS process when the proxyproto plugin is enabled because plugin/pkg/proxyproto/proxyproto.go PacketConn.ReadFrom handles a PROXY v2 header with non-UDP transport such as family byte 0x11,…
When was CVE-2026-62309 disclosed?
CVE-2026-62309 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-62309 actively exploited?
CVE-2026-62309 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 50.6% of all scored CVEs.
What is the CVSS score of CVE-2026-62309?
CVE-2026-62309 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-62309?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62309, 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-62309

Explore →

Is Your Infrastructure Affected by CVE-2026-62309?

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

Start Free Scan →Browse All CVEs