CVE-2026-62309

HIGHPre-NVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 7.5Exploit: NoneExposed: 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.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(low)
EPSS
—
KEV
Not listed

Published

July 16, 2026

Last Modified

July 18, 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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 2× 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-07-16 20:10 UTCEG score recompute
  2. 2026-07-16 20:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

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 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-62309?
CVE-2026-62309 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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