Skip to content
fr Sign in
9.1 Critical

CVE-2025-68121 During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between…

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.

Affected products and versions

Product Affected versions Fixed in
crypto/tls 1.26 1.26.0-rc.1 → < 1.26.0-rc.3 1.26.0-rc.3
crypto/tls 1.25 1.25.0-0 → < 1.25.7 1.25.7
crypto/tls 1.24 earliest → < 1.24.13 1.24.13

References

Timeline

  1. Published
  2. Last modified

Other CVEs of crypto/tls

The 13 CVEs of crypto/tls →
CVE-2026-97031 Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted… 7.5 High CVE-2026-56862 Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has… 7.5 High CVE-2026-42505 Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of… 5.3 Medium CVE-2026-32283 If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection… 7.5 High
Track this CVE