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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-40975: 0.31% estimated exploitation activity in the next 30 days; percentile 24.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

28 Apr 2026, 00:31 UTC

Last modified by the source

6 May 2026, 18:54 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m4x9-hx6x-2c43

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-40975

Advisory: Spring Boot's random value property source uses a weak PRNG unsuitable for secrets
IDs: CVE-2026-40975, GHSA-m4x9-hx6x-2c43
Record: https://patchnext.com/advisories/cve-2026-40975 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.springframework.boot:spring-boot-cassandra 4.0.6, 3.5.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework.boot:spring-boot-cassandra: affected >= 4.0.0, < 4.0.6; >= 3.5.0, < 3.5.14; >= 3.4.0, <= 3.4.15; >= 3.3.0, <= 3.3.18; <= 2.7.32; fixed in 4.0.6, 3.5.14

## Suggested inspection (read-only)
- Maven org.springframework.boot:spring-boot-cassandra: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.springframework.boot:spring-boot-cassandra.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m4x9-hx6x-2c43 (GitHub-reviewed advisory GHSA-m4x9-hx6x-2c43 lists affected ranges: Maven org.springframework.boot:spring-boot-cassandra >=4.0.0 =3.5.0 =3.4.0 =3.3.0 =0 <=2.7.32)

Commands are suggestions: review each one before running it.