Spring Data 2024.0 · Version Status
Spring Data 2024.0 End of Life Date
Spring Data 2024.0 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (spring.io); the source of each date is on the product page.
⚠
Spring Data 2024.0 is past end of life. This version no longer receives security patches. EOL since June 2025 — migrate to a supported version immediately.
EOL Date
Jun 2025
EOL since June 2025
Latest Release
2024.0.13
Standard release
Release Date
May 17, 2024
Spring Data 2024.0 series
Extended Support
Jun 2026
Tanzu Spring commercial support · paid · ended
Where these dates come from
End of lifeJun 2025Vendor's own page, read by our adapter · spring.io · checked Nov 18, 2026high · 2 sources agree End of extended supportJun 2026Vendor's own page, read by our adapter · spring.io · checked Nov 18, 2026high · 2 sources agree ReleaseMay 17, 2024Our catalog, built from the vendor pages · spring.iomedium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Spring Data 2024.0 was released on May 17, 2024 and support ended in June 2025 — a supported lifespan of 1 year and 1 month, in line with the 1 year and 2 months median for Spring Data releases. Its latest release on record is 2024.0.13, published June 13, 2025 — in the month support ended. It has been past its end-of-life date for 1 year and 5 months. 2 newer Spring Data releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Spring Data 2024.0 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
| 2020.0 |
2020.0.15 |
Nov 2021 |
EOL |
| 2021.0 |
2021.0.12 |
May 2022 |
EOL |
| 2021.1 |
2021.1.10 |
Nov 2022 |
EOL |
| 2021.2 |
2021.2.18 |
Jun 2023 |
EOL |
| 2022.0 |
2022.0.12 |
Dec 2023 |
EOL |
| 2023.0 |
2023.0.12 |
Jun 2024 |
EOL |
| 2023.1 |
2023.1.12 |
Dec 2024 |
EOL |
| → 2024.0 |
2024.0.13 |
Jun 2025 |
EOL |
What does Spring Data 2024.0 end of life mean?
When Spring Data 2024.0 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Spring Data 2024.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Spring Data 2026.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Spring Data 2024.0 reach end of life?
Spring Data 2024.0 reached end of life in June 2025. This version is no longer receiving security patches.
Is Spring Data 2024.0 still supported?
No. Spring Data 2024.0 reached end of life in June 2025 and is no longer receiving security patches.
What should I upgrade to from Spring Data 2024.0?
The recommended upgrade from Spring Data 2024.0 is
Spring Data 2026.0 — the latest actively supported version. Check the
Spring Data full timeline for all supported versions.
What are the security risks of running Spring Data 2024.0 past EOL?
Since Spring Data 2024.0 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Spring Data should migrate immediately or implement compensating controls.