During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated…
Historical advisory recorded 25 Oct 2026 04:17:10 UTC. Read the latest advisory.
nvd · CVE-2025-68121
PublishedDuring 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-68121 · CVE overview and exploitation status
nvd · CVE-2025-68121
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.