CVE-2026-40975

HIGHNVD 7.54.8▼
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
4.8(medium)
EPSS
23.1%
KEV
Not listed

Published

April 28, 2026

Last Modified

June 30, 2026

Advisory Details (8)

Auto-updated Jul 3, 2026
Patch available. Sources: redhat.
redhat Patch Available

Affected: Red Hat Enterprise Linux 8",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40975.json
redhat Patch Available

2463331 – (CVE-2026-40975) CVE-2026-40975 Spring Boot: Spring Boot: Weak pseudo-random number generation can lead to information disclosure.

https://bugzilla.redhat.com/show_bug.cgi?id=2463331
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-40975
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:25089
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:22619
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:21772
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:17668
generic

CVE-2026-40975: Random value property source uses a weak PRNG unsuitable for secrets

https://spring.io/security/cve-2026-40975

Vendor Advisories for CVE-2026-40975(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatspring-boot2026-06-10redhat
redhatdevspaces/pluginregistry-rhel9:17793594232026-05-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.springframework.boot:spring-boot-cassandra———

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 102 total refreshes for this CVE.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 04:33 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-24 14:05 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-19 19:25 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-17 17:53 UTCEPSS rescore
  6. 2026-06-16 17:52 UTCEPSS rescore
  7. 2026-06-15 17:49 UTCEPSS rescore
  8. 2026-06-14 10:52 UTCEG score recompute
  9. 2026-06-14 10:52 UTCVendor advisory
  10. 2026-06-13 23:00 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 10:38 UTCEG score recompute
  14. 2026-06-12 10:38 UTCVendor advisory
  15. 2026-06-11 14:00 UTCEPSS rescore
  16. 2026-06-11 09:53 UTCEG score recompute
  17. 2026-06-11 09:53 UTCVendor advisory
  18. 2026-06-10 22:18 UTCEPSS rescore
  19. 2026-06-10 13:22 UTCEPSS rescore
  20. 2026-06-10 13:22 UTCEPSS rescore
  21. 2026-06-10 09:14 UTCEG score recompute
  22. 2026-06-10 09:14 UTCVendor advisory
  23. 2026-06-09 09:42 UTCEG score recompute
  24. 2026-06-09 09:42 UTCVendor advisory
  25. 2026-06-08 14:17 UTCEPSS rescore
  26. 2026-06-08 14:17 UTCEPSS rescore
  27. 2026-06-08 09:33 UTCEG score recompute
  28. 2026-06-08 09:33 UTCVendor advisory
  29. 2026-06-07 15:25 UTCEPSS rescore
  30. 2026-06-07 15:25 UTCEPSS rescore
  31. 2026-06-07 10:00 UTCEG score recompute
  32. 2026-06-07 10:00 UTCVendor advisory
  33. 2026-06-06 13:47 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-06 10:24 UTCEG score recompute
  36. 2026-06-06 10:24 UTCVendor advisory
  37. 2026-06-05 22:47 UTCEPSS rescore
  38. 2026-06-05 10:18 UTCEG score recompute
  39. 2026-06-05 10:18 UTCVendor advisory
  40. 2026-06-05 06:10 UTCEPSS rescore
  41. 2026-06-05 06:10 UTCEPSS rescore
  42. 2026-06-04 13:12 UTCEPSS rescore
  43. 2026-06-04 13:12 UTCEPSS rescore
  44. 2026-06-04 10:25 UTCEG score recompute
  45. 2026-06-04 10:25 UTCVendor advisory
  46. 2026-06-03 10:42 UTCEG score recompute
  47. 2026-06-03 10:42 UTCVendor advisory
  48. 2026-06-02 20:13 UTCEPSS rescore
  49. 2026-06-02 11:07 UTCEG score recompute
  50. 2026-06-02 11:07 UTCVendor advisory
  51. 2026-06-01 13:52 UTCEPSS rescore
  52. 2026-06-01 13:52 UTCEPSS rescore
  53. 2026-06-01 13:51 UTCEPSS rescore
  54. 2026-06-01 11:33 UTCEG score recompute
  55. 2026-06-01 11:33 UTCVendor advisory
  56. 2026-05-31 22:30 UTCEPSS rescore
  57. 2026-05-31 22:30 UTCEPSS rescore
  58. 2026-05-31 00:16 UTCEPSS rescore
  59. 2026-05-31 00:16 UTCEPSS rescore
  60. 2026-05-31 00:16 UTCEPSS rescore
  61. 2026-05-29 13:44 UTCEPSS rescore
  62. 2026-05-29 13:44 UTCEPSS rescore
  63. 2026-05-28 13:44 UTCEPSS rescore
  64. 2026-05-28 13:44 UTCEPSS rescore
  65. 2026-05-28 13:44 UTCEPSS rescore
  66. 2026-05-27 13:40 UTCEPSS rescore
  67. 2026-05-27 13:40 UTCEPSS rescore
  68. 2026-05-27 13:40 UTCEPSS rescore
  69. 2026-05-26 13:44 UTCEPSS rescore
  70. 2026-05-26 07:18 UTCEPSS rescore
  71. 2026-05-26 07:18 UTCEPSS rescore
  72. 2026-05-23 00:08 UTCEG score recompute
  73. 2026-05-20 22:38 UTCEPSS rescore
  74. 2026-05-20 22:38 UTCEPSS rescore
  75. 2026-05-20 15:24 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-40975?
CVE-2026-40975 is a high vulnerability published on April 28, 2026. 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),…
When was CVE-2026-40975 disclosed?
CVE-2026-40975 was first published in the National Vulnerability Database on April 28, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40975 actively exploited?
CVE-2026-40975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40975?
CVE-2026-40975 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 4.8.
How do I remediate CVE-2026-40975?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40975, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40975

Explore →

Is Your Infrastructure Affected by CVE-2026-40975?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs