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.
History

Thu, 05 Feb 2026 18:00:00 +0000

Type Values Removed Values Added
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.
Title Unexpected session resumption in crypto/tls
References

cve-icon MITRE

Status: PUBLISHED

Assigner: Go

Published:

Updated: 2026-02-05T17:48:44.141Z

Reserved: 2025-12-15T16:48:04.451Z

Link: CVE-2025-68121

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-02-05T18:16:10.857

Modified: 2026-02-05T18:16:10.857

Link: CVE-2025-68121

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.