CVE-2026-40975

Values produced by ${random.value} are not suitable for use as secrets. ${random.uuid} is not affected. ${random.int} and ${random.long} should never be used for secrets as they are numeric values with a predictable range.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); random value property source / weak PRNG for secrets. Versions that are no longer supported are also affected per vendor advisory.

Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.

CVE-2026-40975 has a CVSS score of 4.8 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.0.6, 3.5.14); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-40975? CVE-2026-40975 is a medium-severity use of insufficiently random values vulnerability in org.springframework.boot:spring-boot-cassandra (maven), affecting versions >= 4.0.0, < 4.0.6. It is fixed in 4.0.6, 3.5.14. Security-sensitive operations rely on values that are predictable or insufficiently random.
2. How severe is CVE-2026-40975? CVE-2026-40975 has a CVSS score of 4.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.springframework.boot:spring-boot-cassandra are affected by CVE-2026-40975? org.springframework.boot:spring-boot-cassandra (maven) versions >= 4.0.0, < 4.0.6 is affected.
4. Is there a fix for CVE-2026-40975? Yes. CVE-2026-40975 is fixed in 4.0.6, 3.5.14. Upgrade to this version or later.
5. Is CVE-2026-40975 exploitable, and should I be worried? Whether CVE-2026-40975 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-40975 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-40975?
   • Upgrade org.springframework.boot:spring-boot-cassandra to 4.0.6 or later
   • Upgrade org.springframework.boot:spring-boot-cassandra to 3.5.14 or later