CVE-2026-62309

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (52nd 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

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

7.5EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.7%
EPSS %ILE
52nd
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, and whom BOD 26-04 binds: 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 none (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.

The score's inputs: 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 16, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

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 pull request

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 / EcosystemFix (by version range) / 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 8× in last 7d / 35× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 190 rows 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 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-62309?
CVE-2026-62309 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-62309 published?
The CVE record for CVE-2026-62309 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-62309 actively exploited?
CVE-2026-62309 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62309?
CVE-2026-62309 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62309?
A fix for CVE-2026-62309 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62309 are linked in the Vendor Advisories panel on this page.

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.