Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
10.0
Go TLS session can be resumed despite changed trust settings
published 22 days ago
Summary
The Go TLS library used by several cleanstart components (kube-state-metrics, go‑fips‑1.26, opentelemetry‑collector‑contrib, argo‑workflows, velero) may allow a connection to be resumed even after the list of trusted certificates is altered. This could let an unauthorized client appear trusted and gain access. Update to a Go release that fixes the issue or ensure the trusted certificate lists are set once and never changed during a connection's lifetime.
What to do
- Update cleanstart kube-state-metrics to version 2.18.0-r0.
- Update cleanstart go-fips-1.26 to version 1.25.6-r1.
- Update cleanstart opentelemetry-collector-contrib to version 0.144.0-r0.
- Update cleanstart go-fips-1.26 to version 1.24.11-r0.
- Update cleanstart go-fips-1.26 to version 1.25.5-r0.
- Update cleanstart argo-workflows to version 3.7.15-r0.
- Update cleanstart argo-workflows to version 3.7.17-r0.
- Update cleanstart velero to version 1.16.2-r0.
- Update cleanstart victoriametrics-cluster to version 1.132.0-r0.
- Update cleanstart temporal-server-fips to version 1.31.1-r1.
- Update cleanstart vt-cli to version 1.2.0-r0.
- Update cleanstart go1.25 to version 1.25.5-r1.
- Update cleanstart velero-plugin-for-aws to version 1.11.1-r1.
- Update cleanstart helm to version 4.0.5-r1.
- Update cleanstart logstash-exporter-fips to version 1.7.1-r0.
- Update cleanstart logstash-exporter-fips to version 1.6.4-r0.
- Update cleanstart logstash-exporter-fips to version 1.9.1-r1.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| CleanStart | cleanstart | kube-state-metrics |
< 2.18.0-r0 Fix: upgrade to 2.18.0-r0
|
| CleanStart | cleanstart | go-fips-1.26 |
< 1.25.6-r1 < 1.24.11-r0 < 1.25.5-r0 Fix: upgrade to 1.25.6-r1
|
| CleanStart | cleanstart | opentelemetry-collector-contrib |
< 0.144.0-r0 Fix: upgrade to 0.144.0-r0
|
| CleanStart | cleanstart | argo-workflows |
< 3.7.15-r0 < 3.7.17-r0 Fix: upgrade to 3.7.15-r0
|
| CleanStart | cleanstart | velero |
< 1.16.2-r0 Fix: upgrade to 1.16.2-r0
|
| CleanStart | cleanstart | victoriametrics-cluster |
< 1.132.0-r0 Fix: upgrade to 1.132.0-r0
|
| CleanStart | cleanstart | temporal-server-fips |
< 1.31.1-r1 Fix: upgrade to 1.31.1-r1
|
| CleanStart | cleanstart | vt-cli |
< 1.2.0-r0 Fix: upgrade to 1.2.0-r0
|
| CleanStart | cleanstart | go1.25 |
< 1.25.5-r1 Fix: upgrade to 1.25.5-r1
|
| CleanStart | cleanstart | velero-plugin-for-aws |
< 1.11.1-r1 Fix: upgrade to 1.11.1-r1
|
| CleanStart | cleanstart | helm |
< 4.0.5-r1 Fix: upgrade to 4.0.5-r1
|
| CleanStart | cleanstart | logstash-exporter-fips |
< 1.7.1-r0 < 1.6.4-r0 < 1.9.1-r1 Fix: upgrade to 1.7.1-r0
|
Original advisory text
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 succ...
CVE-2025-68121 affects multiple packages. 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. See references for individual vulnerability details.
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker full control (estimated)
Timeline
Published30 Oct 2026
Updated31 Oct 2026
First seen31 Oct 2026
Sources
CLEANSTART-2026-IZ72196 · OSV
Track software like this
Free during beta