NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2026-40975 — spring-boot-cassandra

MEDIUM

CVE-2026-40975 is a medium-severity (CVSS 4.8) Insufficient Random Values vulnerability in org.springframework.boot:spring-boot-cassandra. A fix is available for org.springframework.boot:spring-boot-cassandra — see the affected versions and patch details below.

Spring Boot's random value property source uses a weak PRNG unsuitable for secrets

Also known asGHSA-m4x9-hx6x-2c43
Published
Updated
Affected
5 pkgs
Patched
2 / 5
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-40975.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk
0.00%0.30%0.61%0.91%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected
☕org.springframework.boot:spring-boot-cassandra☕org.springframework.boot:spring-boot-cassandra☕org.springframework.boot:spring-boot-cassandra☕org.springframework.boot:spring-boot-cassandra☕org.springframework.boot:spring-boot-cassandra

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

5 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.boot:spring-boot-cassandra≥ 4.0.0&&< 4.0.64.0.6org.springframework.boot:spring-boot-cassandra:4.0.6
☕Mavenorg.springframework.boot:spring-boot-cassandra≥ 3.5.0&&< 3.5.143.5.14org.springframework.boot:spring-boot-cassandra:3.5.14
☕Mavenorg.springframework.boot:spring-boot-cassandra≥ 3.4.0No fix
☕Mavenorg.springframework.boot:spring-boot-cassandra≥ 3.3.0No fix
☕Mavenorg.springframework.boot:spring-boot-cassandraall versionsNo fix

Affected Products

1 product · 5 configurations
Application
spring bootvmware
≥ 4.0.0 && < 4.0.6
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-cassandra, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.springframework.boot:spring-boot-cassandra to 4.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40975 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
Workaround published by Red Hat
Applications utilizing Spring Boot should avoid using the `${random.value}` property for generating cryptographic secrets or other security-sensitive data. Developers should review their application configurations and code to ensure that only cryptographically strong random number generators are used for such purposes. For UUID generation, `${random.uuid}` is not affected and can be used.
Source: Red Hat security advisory for CVE-2026-40975 (CC BY 4.0)
ProductFixed inAdvisory
AMQ Clients 2026.Q3spring-bootRHSA-2026:69459
HawtIO HawtIO 4.4.0spring-bootRHSA-2026:25089
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14spring-bootRHSA-2026:17668
Red Hat Data Grid 8.6.1spring-bootRHSA-2026:22619
Red Hat OpenShift Dev Spaces 3.28devspaces/openvsx-rhel9:1779528224RHSA-2026:21772

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-40975 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-40975: spring-boot-cassandra — Fixed in 4.0.6