CVE-2025-68121: critical vulnerability in Go standard library crypto/tls
Unexpected session resumption in crypto/tls
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.1epss 0.9%
During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
Go standard library · crypto/tlsRelated CVEs — Go standard library crypto/tls
In the same product, most dangerous first.
CVE-2023-29409—Large RSA keys can cause high CPU usage in crypto/tlsEPSS 1.6%CVE-2023-39322—Memory exhaustion in QUIC connection handling in crypto/tlsEPSS 1.3%CVE-2023-39321—Panic when processing post-handshake message on QUIC connections in crypto/tlsEPSS 1.3%CVE-2023-45287—Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channelEPSS 1.3%CVE-2022-30629LOWSession tickets lack random ticket_age_add in crypto/tlsEPSS 1.2%CVE-2022-41724—Panic on large handshake records in crypto/tlsEPSS 1.1%