CVE-2025-68121 | Unexpected session resumption in crypto/tls

Exp

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.

Published: 2026-02-05 Last update: 2026-04-29 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-68121 is rated High Exploit Risk (73.4/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.77%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-68121

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-68121

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.77% +0.76%
2 2026-02-06 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-68121

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
10.0 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 6.0 [email protected]
9.1 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-68121

OS Trackers for CVE-2025-68121

vendor priority summary link
alpine — CVE-2025-68121: 1 source package rows (go); 94 state rows across 2 repos (3.23-community, edge-community); fixed 6, open 88. https://security.alpinelinux.org/vuln/CVE-2025-68121
debian not yet assigned CVE-2025-68121 not yet assigned priority: Debian including 4 source packages (golang-1.15, golang-1.19, golang-1.24, golang-1.25), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-68121
redhat medium — https://access.redhat.com/security/cve/CVE-2025-68121
suse high CVE-2025-68121 severity important: SUSE including 211 source package names (13.2-9.2:curl-8.6.0-5.1, 13.2-9.2:iputils-20221126-6.1, …), 669 product×package rows across 68 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (68 product lines)): Fixed 623, Known Not Affected 32, First Fixed 14. https://www.suse.com/security/cve/CVE-2025-68121/
ubuntu medium CVE-2025-68121 medium priority: Ubuntu including 16 source packages (golang, golang-1.10, …), 98 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): DNE 46, needed 26, not-affected 17, needs-triage 9. https://ubuntu.com/security/CVE-2025-68121

Affected software / configurations for CVE-2025-68121

Vendor Product Version Raw CPE
golang go < 1.24.13 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*
golang go >= 1.25.0, < 1.25.7 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*
golang go 1.26.0 cpe:2.3:a:golang:go:1.26.0:rc1:*:*:*:*:*:*
golang go 1.26.0 cpe:2.3:a:golang:go:1.26.0:rc2:*:*:*:*:*:*

References for CVE-2025-68121

cvelogic Threat Intelligence