CVE-2025-59530 | quic-go has Client Crash Due to Premature HANDSHAKE_DONE Frame

quic-go is an implementation of the QUIC protocol in Go. In versions prior to 0.49.0, 0.54.1, and 0.55.0, a misbehaving or malicious server can cause a denial-of-service (DoS) attack on the quic-go client by triggering an assertion failure, leading to a process crash. This requires no authentication and can be exploited during the handshake phase. This was observed in the wild with certain server implementations. quic-go needs to be able to handle misbehaving server implementations, including those that prematurely send a HANDSHAKE_DONE frame. Versions 0.49.0, 0.54.1, and 0.55.0 discard Initial keys when receiving a HANDSHAKE_DONE frame, thereby correctly handling premature HANDSHAKE_DONE frames.

Published: 2025-10-10 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-59530 is rated Low Risk (33.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.03%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-59530

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-08 0.06% 0.03% -0.03%
2 2025-10-11 — 0.06% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-59530

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-59530

GitHub Security Advisory for CVE-2025-59530

GHSA-47m2-4cr7-mhcw · Severity: high · Ecosystem: go — quic-go: Panic occurs when queuing undecryptable packets after handshake completion

OS Trackers for CVE-2025-59530

vendor priority summary link
debian not yet assigned CVE-2025-59530 not yet assigned priority: Debian including 1 source packages (golang-github-lucas-clemente-quic-go), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-59530
redhat medium — https://access.redhat.com/security/cve/CVE-2025-59530
ubuntu medium CVE-2025-59530 medium priority: Ubuntu including 1 source packages (golang-github-lucas-clemente-quic-go), 5 status rows across 5 suites (jammy, noble, plucky, questing, upstream): needs-triage 3, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-59530

Affected software / configurations for CVE-2025-59530

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-59530

cvelogic Threat Intelligence