CyberSecBulletin
CVE-2026-40975NVD status: Modified

Spring Boot: Use of Insufficiently Random Values

Published Updated By the CyberSecBulletin desk

CVE-2026-40975 is a high-severity use of insufficiently random values vulnerability in Spring Boot from Spring, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.0.6, 3.5.14, 3.4.16 as the first without the flaw, so updating Spring Boot to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.31% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Spring Boot to 4.0.6 or 3.5.14 or 3.4.16 or 3.3.19, whichever matches your release line, or a later version.
  2. Read the advisory on spring.io for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
SpringSpring Boot4.0.0 up to, but not including, 4.0.6; 3.5.0 up to, but not including, 3.5.14; 3.4.0 up to, but not including, 3.4.16; 3.3.0 up to, but not including, 3.3.19; 2.7.0 up to, but not including, 2.7.334.0.6, 3.5.14, 3.4.16, 3.3.19, 2.7.33
Red HatHawtIO HawtIO 4.4.0Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14Not specified in the recordNot stated
Red HatRed Hat Data Grid 8.6.1Not specified in the recordNot stated
Red HatRed Hat OpenShift Dev Spaces 3.28Not specified in the recordNot stated
Red HatRed Hat AMQ Broker 7Not specified in the recordNot stated
Red HatRed Hat AMQ ClientsNot specified in the recordNot stated
Red HatRed Hat build of OptaPlanner 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackNot specified in the recordNot stated
Red HatRed Hat Process Automation 7Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.14.8MediumCNA (vmware.com)
CVSS 3.17.5HighNVD
CVSS 3.18.2HighCNA

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of Insufficiently Random Values

The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.

How developers prevent this class of flaw

  • Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds. In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts. Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a random enough number.
  • Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
  • Use products or modules that conform to FIPS 140-2 to avoid obvious entropy problems. Consult FIPS 140-2 Annex C (Approved Random Number Generators).

More Use of Insufficiently Random Values vulnerabilities (CWE-330)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Spring Boot

All Spring Boot vulnerabilities

Recent Use of Insufficiently Random Values vulnerabilities

Spotted an error? Tell us.