dbcve.org
Spring BootFramework / library · VMware

CVE-2026-40975

HIGH · 7.5 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 2.7.33 / 3.3.19 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ${random.value} property placeholder in Spring Boot uses a weak pseudo-random number generator (PRNG) that produces predictable values, making it unsuitable for generating secrets such as passwords, tokens, or encryption keys. This contrasts with ${random.uuid} which is not affected, while ${random.int} and ${random.long} have predictable numeric ranges that make them inherently unsuitable for secrets.

MitigationUpgrade Spring Boot to the fixed versions (4.0.6, 3.5.14, 3.4.16, 3.3.19, or 2.7.33) and audit any existing uses of ${random.value} in configuration files to replace with proper secret management mechanisms.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring BootFramework / library
Affected:< 2.7.33>= 3.3.0, < 3.3.19>= 3.4.0, < 3.4.16>= 3.5.0, < 3.5.14>= 4.0.0, < 4.0.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Boot version
    Check your project pom.xml or build.gradle for the spring-boot-starter parent version, or check the spring-boot-version file if using the runtime distribution
    Affected if version is < 2.7.33 OR >= 3.3.0 and < 3.3.19 OR >= 3.4.0 and < 3.4.16 OR >= 3.5.0 and < 3.5.14 OR >= 4.0.0 and < 4.0.6
  2. Search for random value placeholders in configuration
    Grep for ${random.value}, ${random.int}, or ${random.long} in all .properties and .yaml/.yml files in your configuration directories (src/main/resources, config/, or deployed config files)
    Affected if any of these placeholders are found in configuration files
  3. Identify usage context for random placeholders
    Review the configuration keys containing random placeholders and determine if they are used for secrets, passwords, tokens, API keys, encryption keys, or other sensitive values
    Affected if random placeholders are assigned to properties that hold secrets or sensitive data such as passwords, keys, tokens, or credentials

You are affected if your Spring Boot version falls within the vulnerable ranges AND your configuration files contain ${random.value}, ${random.int}, or ${random.long} used for secrets or sensitive values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.33 / 3.3.19 / 3.4.16 or later
Fixed in 2.7.333.3.193.4.16
Interim mitigation

Upgrade Spring Boot to the fixed versions (4.0.6, 3.5.14, 3.4.16, 3.3.19, or 2.7.33) and audit any existing uses of ${random.value} in configuration files to replace with proper secret management mechanisms.

Recommended fix High confidence

Upgrade to Spring Boot 2.7.33, 3.3.19, 3.4.16, 3.5.14, or 4.0.6 depending on your current major version line

  1. Identify current Spring Boot version in use by checking pom.xml or build.gradle
  2. Determine the appropriate upgrade target based on current major version line
  3. Upgrade Spring Boot version in pom.xml or build.gradle to the fixed version (2.7.33 for 2.x, 3.3.19 for 3.3.x, 3.4.16 for 3.4.x, 3.5.14 for 3.5.x, or 4.0.6 for 4.x)
  4. Run mvn clean install or ./gradlew build to verify the upgrade compiles successfully
  5. Review application.properties and application.yml for any usage of ${random.value}, ${random.int}, or ${random.long} as secrets
  6. Replace any insecure random property usages with proper secrets management (e.g., environment variables, Vault, or proper secret generation)
  7. Run full test suite to ensure no regressions
Caveat Review Spring Boot migration guides as minor version upgrades may include dependency updates and configuration changes; test thoroughly before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Boot Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40975 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data