CVE-2025-68121
CWE-295Published: February 5, 2026· Updated: Jun 17, 2026
Official Description
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.
Risk Analysis
A flaw in TLS session resumption allows for successful handshakes even when CA configurations are mutated, potentially leading to unauthorized session resumption. Given the critical CVSS score of 10.0, this represents a significant risk to secure communication integrity.
No public exploit is currently known, and the vulnerability is not in the CISA KEV database.
Upgrade to a patched version of Go that addresses this session resumption logic error.
Technical Analysis
CVE-2025-68121 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.
The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.
A successful exploit results in complete confidentiality breach (data exposure), full integrity compromise (data manipulation), availability disruption (denial of service), with a CVSS base score of 10.0.
The vulnerability has a "Changed" scope, meaning successful exploitation can impact components beyond the vulnerable component itself — such as the host operating system or adjacent services.
CVSS v3.1 Vector Breakdown
Affected Vendors & Products
Exploit & PoC Resources
Official Patches & Advisories
All References (4)
Quick Facts
Related CVEs (CWE-295)
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2025-68121 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts