CVE-2026-40975

HIGH
7.5
CVSS Score
Published: April 27, 2026 at 11:32 PM UTC
Updated: July 24, 2026 at 09:10 PM UTC
5 products affected across 3 vendorsSpring BootFuseJBoss Amq Clients

Using Spring Boot by Spring?

Get instant alerts when new vulnerabilities affect Spring Boot - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.7.333.3.0 ≤ v < 3.3.193.4.0 ≤ v < 3.4.163.5.0 ≤ v < 3.5.144.0.0 ≤ v < 4.0.6
Affected range stops below 2.7.33, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.6, so it looks safe — our inference, not a vendor statement
All versions
2.7.0 ≤ v < 2.7.333.3.0 ≤ v < 3.3.193.4.0 ≤ v < 3.4.163.5.0 ≤ v < 3.5.144.0.0 ≤ v < 4.0.62.7.03.3.03.4.03.5.04.0.0
Affected range stops below 2.7.33, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.6, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (8)

Vendor Advisory
Source: cverecord
https://spring.io/security/cve-2026-40975
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:17668
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:21772
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:22619
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:25089
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-40975
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2463331

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-330CWE-338

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card