CVE-2025-68121 is a flaw in Go's crypto/tls session resumption logic. During a resumed TLS handshake, if the underlying tls.Config has its ClientCAs or RootCAs fields changed after the original handshake but before the resumed handshake, the resumption can succeed even though a full handshake under the new configuration should have failed. The issue can arise when an application clones a tls.Config and then mutates the returned configuration, or when it uses GetConfigForClient to supply configurations whose trust settings differ over time. As a result, certificate validation decisions made for the resumed session may no longer reflect the current trust anchors or client authentication policy, leading to incorrect acceptance of a peer during session resumption.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
173 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A certificate validation flaw in Go's crypto/tls during TLS session resumption.
A Go crypto/tls vulnerability involving incorrect certificate validation during TLS session resumption.
A crypto/tls flaw involving unexpected TLS session resumption behavior.
A Go crypto/tls flaw involving incorrect certificate validation or unexpected TLS session resumption.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.