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.0%, top 99% 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.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

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.0(medium)
EPSS
3.4%
KEV
Not listed

Published

April 28, 2026

Last Modified

April 30, 2026

Advisory Details (1)

Auto-updated Jun 11, 2026
No patch confirmed yet.
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 / 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-boot1.0.0.RELEASE ... 2.7.9 (186 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

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

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 in the National Vulnerability Database on April 28, 2026, with the most recent update on April 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-40973 actively exploited?
CVE-2026-40973 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40973, 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-40973

Explore →

Is Your Infrastructure Affected by CVE-2026-40973?

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

Start Free Scan →Browse All CVEs