CVE-2026-40973

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% 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.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A local attacker on the same host as the application may be able to take control of the directory used by ApplicationTemp. When server.servlet.session.persistent is set to true and the attack persists across application restarts, this may allow the attacker to read session information and hijack authenticated users or deploy a gadget chain and execute code as the application's user.

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); predictable temp directory / ApplicationTemp ownership verification. Versions that are no longer supported are also affected per vendor advisory.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

Published

April 28, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jun 11, 2026
Patch available.
generic

CVE-2026-40973: Predictable temp directory accepted without ownership verification

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

Vendor Advisories for CVE-2026-40973(3)

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
org.springframework.boot:spring-boot1.0.0.RELEASE ... 2.7.9 (186 versions)
  • 4.0.0 up to 4.0.6: fixed in 4.0.6
  • 3.5.0 up to 3.5.14: fixed in 3.5.14
  • 3.4.0 through 3.4.15: no fix on record
  • 3.3.0 through 3.3.18: no fix on record
  • every version through 2.7.32: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 24× 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 212 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-40973?
CVE-2026-40973 is a high vulnerability published on April 28, 2026. A local attacker on the same host as the application may be able to take control of the directory used by ApplicationTemp. When server.servlet.session.persistent is set to true and the attack persists across application restarts, this may allow the attacker to read session information and hijack…
When was CVE-2026-40973 disclosed?
CVE-2026-40973 was first published on April 28, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40973 actively exploited?
CVE-2026-40973 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40973?
CVE-2026-40973 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-40973?
A fix for CVE-2026-40973 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40973 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-40973?

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

Book a Demo →Browse All CVEs