Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) Affecting spring-boot package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.06% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-SPRINGBOOT-16789929
  • published21 May 2026
  • disclosed27 Apr 2026

Introduced: 27 Apr 2026

CVE-2026-40975  (opens in a new tab)
CWE-338  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 spring-boot.

NVD Description

Note: Versions mentioned in the description apply only to the upstream spring-boot package and not the spring-boot package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1