Security readout for executives and security teams
Plain-English summary
Go’s TLS library may incorrectly reuse a prior secure session after certificate authority settings change. This can let a connection continue where a fresh TLS handshake would have been rejected. The risk matters for services relying on client certificates or changing trust roots dynamically.
Executive priority
Treat as high-priority for Go-based services that use TLS client certificates or runtime trust changes. Business urgency is lower for services with static TLS configuration and no relevant resumption behavior, but confirmation is needed.
Technical view
CVE-2025-68121 affects Go standard library crypto/tls session resumption. If Config.ClientCAs or Config.RootCAs is mutated between the original and resumed handshake, resumption may succeed incorrectly. Sources cite Config.Clone mutation and GetConfigForClient as relevant patterns. The issue maps to CWE-295 and has CVSS 9.1.
Likely exposure
Exposure is most likely in Go applications using crypto/tls with session resumption and dynamic or cloned TLS configurations that change ClientCAs or RootCAs. Mutual TLS deployments, multi-tenant TLS selection, and systems rotating trust stores at runtime warrant review.
Exploitation context
No source provided indicates active exploitation, and KEV is false. The risk is network-reachable because TLS handshakes occur remotely, but exploitation depends on application-specific TLS configuration behavior and whether trust settings mutate between handshakes.
Researcher notes
The provided bundle names affected crypto/tls versions and the failure condition, but does not include fixed version details. Analysis should focus on resumed handshakes after trust configuration mutation, without assuming exploit availability or universal impact across all Go TLS users.
Mitigation direction
- Review Go advisory and release notes for fixed Go versions before deploying changes.
- Inventory Go services using crypto/tls, Config.Clone, or GetConfigForClient.
- Avoid mutating ClientCAs or RootCAs on configurations used for resumable sessions.
- Prioritize mTLS and dynamic trust-store services for remediation review.
Validation and detection
- Identify deployed Go versions and crypto/tls usage in affected services.
- Search code for Config.Clone, GetConfigForClient, ClientCAs, and RootCAs patterns.
- Confirm whether TLS session resumption is enabled in reviewed services.
- Verify vendor advisory status and document upgrade or compensating-control decisions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-68121 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://groups.google.com/g/golang-announce/c/K09ubi9FQFkCVE reference
- https://go.dev/cl/737700CVE reference
- https://go.dev/issue/77217CVE reference
- https://pkg.go.dev/vuln/GO-2026-4337CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.