Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
10.0
TLS session resumption can bypass certificate checks in cleanstart tools
published 21 days ago
Summary
The TLS library used by several cleanstart applications can incorrectly accept a resumed connection if the list of trusted certificates is changed after the first handshake. This means an attacker could continue a session that should have been rejected, potentially gaining unauthorized access. Update the affected software to the latest version or ensure the trusted‑certificate settings are not altered during a session.
What to do
- Update cleanstart coredns-fips to version 1.14.1-r0.
- Update cleanstart step-cli to version 0.28.7-r3.
- Update cleanstart nats-server-config-reloader-fips to version 0.21.1-r0.
- Update cleanstart gatekeeper to version 3.20.1-r1.
- Update cleanstart gatekeeper-fips to version 3.20.1-r1.
- Update cleanstart nats-server-config-reloader-fips to version 0.20.1-r0.
- Update cleanstart nats-server-fips to version 2.9.25-r1.
- Update cleanstart newrelic-k8s-metadata-injection to version 1.39.2-r0.
- Update cleanstart nats-server-config-reloader-fips to version 0.19.3-r0.
- Update cleanstart nats-server-fips to version 2.10.29-r4.
- Update cleanstart kyverno-policy-reporter-ui-fips to version 2.4.4-r2.
- Update cleanstart cloudflared to version 2025.11.1-r2.
- Update cleanstart go-fips-1.24 to version 1.24.11-r0.
- Update cleanstart go-fips-1.24 to version 1.24.12-r1.
- Update cleanstart go-fips-1.24 to version 1.25.5-r0.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| CleanStart | cleanstart | coredns-fips |
< 1.14.1-r0 Fix: upgrade to 1.14.1-r0
|
| CleanStart | cleanstart | step-cli |
< 0.28.7-r3 Fix: upgrade to 0.28.7-r3
|
| CleanStart | cleanstart | nats-server-config-reloader-fips |
< 0.21.1-r0 < 0.20.1-r0 < 0.19.3-r0 Fix: upgrade to 0.21.1-r0
|
| CleanStart | cleanstart | gatekeeper |
< 3.20.1-r1 Fix: upgrade to 3.20.1-r1
|
| CleanStart | cleanstart | gatekeeper-fips |
< 3.20.1-r1 Fix: upgrade to 3.20.1-r1
|
| CleanStart | cleanstart | nats-server-fips |
< 2.9.25-r1 < 2.10.29-r4 Fix: upgrade to 2.9.25-r1
|
| CleanStart | cleanstart | newrelic-k8s-metadata-injection |
< 1.39.2-r0 Fix: upgrade to 1.39.2-r0
|
| CleanStart | cleanstart | kyverno-policy-reporter-ui-fips |
< 2.4.4-r2 Fix: upgrade to 2.4.4-r2
|
| CleanStart | cleanstart | cloudflared |
< 2025.11.1-r2 Fix: upgrade to 2025.11.1-r2
|
| CleanStart | cleanstart | go-fips-1.24 |
< 1.24.11-r0 < 1.24.12-r1 < 1.25.5-r0 Fix: upgrade to 1.24.11-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
Published31 Oct 2026
Updated31 Oct 2026
First seen31 Oct 2026
Sources
CLEANSTART-2026-MU58230 · OSV
Track software like this
Free during beta