CVE-2025-68121
Unexpected session resumption in crypto/tls
Reported by go · Published February 5, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| timoni | Chainguard | 0.25.2-r5 |
| etcd-3.6 | Wolfi | 3.6.7-r3 |
| gitlab-workhorse-ce-fips-18.1 | Chainguard | 18.1.6-r5 |
| go-fdo-server-debugsource | errata.rockylinux.org | 1.0.1-2.el10 |
| direnv | Wolfi | 2.37.1-r5 |
| prometheus-blackbox-exporter-fips | Chainguard | 0.28.0-r2 |
| neuvector-fips | Chainguard | 5.4.9-r0 |
| docker-machine-driver-harvester | Chainguard | 1.0.6-r1 |
| haproxy-ingress | Chainguard | 0.15.1-r3 |
| nri-redis-fips | Chainguard | 1.12.8-r1 |
| skopeo-debugsource | errata.rockylinux.org | 2:1.20.0-3.el9_7.x86_64 |
| prometheus-redis-exporter-fips | Chainguard | 1.81.0-r0 |
87 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Go standard library | crypto/tls | 0, 1.25.0-0, 1.26.0-rc.1 |
| chainguard | timoni | 0 |
| wolfi | etcd-3.6 | 0 |
| chainguard | gitlab-workhorse-ce-fips-18.1 | 0 |
| wolfi | direnv | 0 |
| chainguard | prometheus-blackbox-exporter-fips | 0 |
| chainguard | neuvector-fips | 0 |
| chainguard | docker-machine-driver-harvester | 0 |
| chainguard | haproxy-ingress | 0 |
| chainguard | nri-redis-fips | 0 |
| chainguard | prometheus-redis-exporter-fips | 0 |
| chainguard | aws-sigv4-proxy-fips | 0 |
| chainguard | kubelet-csr-approver-fips | 0 |
| wolfi | boring-registry | 0 |
| chainguard | cloud-provider-aws-1.29 | 0 |
| wolfi | velero-plugin-for-csi | *, 0 |
| chainguard | vault-fips-1.21 | 0 |
| chainguard | tekton-pipelines-0.62 | *, 0 |
| chainguard | elastic-agent-9.2 | 0 |
| chainguard | cloud-provider-aws-1.30 | 0 |
…and 2469 more
Timeline
- Jan 15, 2026 CVE Published
- Feb 6, 2026 EPSS Score (30 in total, the first dated here)
- Mar 17, 2026 Distribution Patch (360 in total, the first dated here)
- Mar 17, 2026 Security Advisory (347 in total, the first dated here)
- Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-68121
vulnetix vdb fixes CVE-2025-68121Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-68121/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart