Improper Certificate Validation Affecting std/crypto/tls package, versions <1.24.13>=1.25.0-0 <1.25.7>=1.26.0-rc.1 <1.26.0-rc.3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-STDCRYPTOTLS-15238826
- published6 Feb 2026
- disclosed5 Feb 2026
- creditCoia Prant, Go Security Team
Introduced: 5 Feb 2026
CVE-2025-68121 (opens in a new tab)How to fix?
Upgrade std/crypto/tls to version 1.24.13, 1.25.7, 1.26.0-rc.3 or higher.
Overview
std/crypto/tls is a Go standard library package std/crypto/tls
Affected versions of this package are vulnerable to Improper Certificate Validation.
Go Vulnerability Report:
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.