Authentication bypass via stale session trust state
Published Feb 5, 2026 · Updated Feb 5, 2026
Improper certificate validation in Go crypto/tls allows remote attackers to resume TLS sessions against changed trust settings. Session resumption retains the earlier handshake trust decision instead of rechecking mutated ClientCAs or RootCAs in Config.Clone or GetConfigForClient configurations. Exposure requires an application to change those trust pools between the initial and resumed handshakes, allowing a previously accepted peer to bypass the new trust policy.
Summary
What happened
Improper certificate validation in Go crypto/tls allows remote attackers to resume TLS sessions against changed trust settings. Session resumption retains the earlier handshake trust decision instead of rechecking mutated ClientCAs or RootCAs in Config.Clone or GetConfigForClient configurations. Exposure requires an application to change those trust pools between the initial and resumed handshakes, allowing a previously accepted peer to bypass the new trust policy.
The record
- CVE
- CVE-2025-68121
- Published
- Feb 5, 2026
- Updated
- Feb 5, 2026
- Vendor
- Go
- Product
- crypto/tls
- Classifications
- CWE-295
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2026CVE publishedPublication date reported by the CVE source.
- Feb 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.24.13
- Affected versionversion=1.25.0-0 <1.25.7
- Affected versionversion=1.26.0-rc.1 <1.26.0-rc.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo