Secret prediction via noncryptographic random generation
Published Apr 27, 2026 · Updated Apr 27, 2026
Weak random generation in affected Spring Boot releases allows remote attackers to predict secrets derived from ${random.value}. RandomValuePropertySource instantiates java.util.Random rather than a cryptographically secure generator, making its output predictable from recovered PRNG state. Exploitation requires an application to use ${random.value} for a security-sensitive value and expose related output; ${random.uuid} is unaffected.
Summary
What happened
Weak random generation in affected Spring Boot releases allows remote attackers to predict secrets derived from ${random.value}. RandomValuePropertySource instantiates java.util.Random rather than a cryptographically secure generator, making its output predictable from recovered PRNG state. Exploitation requires an application to use ${random.value} for a security-sensitive value and expose related output; ${random.uuid} is unaffected.
The record
- CVE
- CVE-2026-40975
- Published
- Apr 27, 2026
- Updated
- Apr 27, 2026
- Vendor
- Spring
- Product
- Spring Boot
- Classifications
- CWE-338, CWE-330
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 27, 2026CVE publishedPublication date reported by the CVE source.
- Apr 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.7.0 <2.7.33
- Affected versionversion=3.3.0 <3.3.19
- Affected versionversion=3.4.0 <3.4.16
- Affected versionversion=3.5.0 <3.5.14
- Affected versionversion=4.0.0 <4.0.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo