CVE-2026-40975: Weak RNG

Published Apr 27, 2026
·
Updated

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 Software

7 affected components
VMware Spring Boot>=4.0.0<=4.0.5, >=3.5.0<=3.5.13, >=3.4.0<=3.4.15, >=3.3.0<=3.3.18, >=2.7.0<=2.7.32
VMware Spring Boot<2.7.33
VMware Spring Boot>=3.3.0<3.3.19
VMware Spring Boot>=3.4.0<3.4.16
VMware Spring Boot>=3.5.0<3.5.14
VMware Spring Boot>=4.0.0<4.0.6
IBM API Connect V12 OnPrem<=All

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 4.0.6
  2. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 3.5.14
  3. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 3.4.16
  4. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 3.3.19
  5. Upgrade

    Upgrade Spring Boot to a version that resolves this vulnerability.

    Fixed in 2.7.33
  6. Configuration

    Do not use ${random.int}, ${random.long}, or ${random.value} for secrets because they produce numeric values with predictable range / are not suitable for secrets; ${random.uuid} is not affected.

    Spring Boot random value property source secret_generation = Do not use ${random.int}, ${random.long}, or ${random.value} for secrets

Event History

Apr 27, 2026
CVE Published
via MITRE·11:32 PM
Data Sourced
via MITRE·11:32 PM
DescriptionSeverityWeakness
Apr 28, 2026
Data Sourced
via Red Hat·12:02 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeaknessAffected Software
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-40975?

CVE-2026-40975 is classified as a medium severity vulnerability.

2

How do I fix CVE-2026-40975?

To fix CVE-2026-40975, upgrade to Spring Boot version 4.0.6, 3.5.14, or any later patched version.

3

What are the affected versions for CVE-2026-40975?

CVE-2026-40975 affects Spring Boot versions 4.0.0 to 4.0.5, 3.5.0 to 3.5.13, and earlier versions below 2.7.32.

4

What potential risks are posed by CVE-2026-40975?

CVE-2026-40975 poses risks related to the generation of predictable secret values, compromising application security.

5

Which methods should be avoided due to CVE-2026-40975?

Due to CVE-2026-40975, methods ${random.int} and ${random.long} should be avoided for generating secrets.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203