Spring Boot 4.0 · Version Status

Spring Boot 4.0 End of Life Date

Spring Boot 4.0 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

⚡ Spring Boot 4.0 reaches end of life in December 2026. Plan your migration now (the vendor names the month only).
📅 Get reminded before Spring Boot 4.0 reaches EOL in December 2026 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Dec 2026
EOL in December 2026
Latest Release
4.0.9
Standard release
Release Date
Nov 20, 2025
Spring Boot 4.0 series
Extended Support
Dec 2027
Tanzu Spring commercial support · paid
Where these dates come from
End of lifeDec 2026Vendor's own page, read by our adapter · spring.io · checked Nov 3, 2026high · 3 sources agree
End of extended supportDec 2027Vendor's own page, read by our adapter · spring.io · checked Nov 3, 2026high · 3 sources agree
ReleaseNov 20, 2025Vendor's own page (our correction) · github.com · checked Sep 25, 2026medium · 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.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Spring Boot 4.0 was released on November 20, 2025 and support is scheduled to end in December 2026 — a planned supported lifespan of 1 year and 1 month, in line with the 1 year and 1 month median for Spring Boot releases. Its most recent patch is 4.0.9, published October 22, 2026.

← Spring Boot 3.5 All Spring Boot versions Spring Boot 4.1 →
45 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
15/40
Attack Surface
20/30 High tier
CISA KEV Exposure
10/20 Core component in 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 →
Recommended upgrade path
Spring Boot 4.1
Latest release: 4.1.2 · EOL: Jul 2027
View full Spring Boot timeline →
Extended Support
Need Spring Boot 4.0 patched past end of life?

Extended support for Spring Boot exists: vetted vendors ship security patches past the official date. So far there are 130+ post-EOL CVE fixes documented in vendor release notes across the Spring ecosystem. Whether it covers Spring Boot 4.0 is part of what we check. Leave an email and we reply within one business day with matched options and pricing guidance, or an honest "no vendor covers this version." Free, no obligation; vendors do not pay for placement.

All Spring Boot Versions
VersionLatestEOL DateStatus
1.5 1.5.22 Aug 6, 2019 EOL
2.0 2.0.9 Mar 1, 2019 EOL
2.1 2.1.18 Oct 30, 2019 EOL
2.2 2.2.13 Oct 16, 2020 EOL
2.3 2.3.12 May 20, 2021 EOL
2.4 2.4.13 Nov 18, 2021 EOL
2.5 2.5.15 May 19, 2022 EOL
2.6 2.6.15 Nov 24, 2022 EOL

What does Spring Boot 4.0 end of life mean?

When Spring Boot 4.0 reaches end of life, the maintainers stop issuing security patches for this version except under Tanzu Spring commercial support (paid), until Dec 2027. 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 Boot 4.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Spring Boot 4.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Spring Boot 4.0 reach end of life?
Spring Boot 4.0 reaches end of life in December 2026. The vendor publishes the month only, not a day.
Is Spring Boot 4.0 still supported?
Spring Boot 4.0 is still supported but approaching end of life in December 2026. Begin planning your migration now.
What should I upgrade to from Spring Boot 4.0?
The recommended upgrade from Spring Boot 4.0 is Spring Boot 4.1 — the latest actively supported version. Check the Spring Boot full timeline for all supported versions.
What are the security risks of running Spring Boot 4.0 past EOL?
When Spring Boot 4.0 reaches end of life, the maintainers stop issuing security patches except under Tanzu Spring commercial support (paid), until Dec 2027. 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 Boot should migrate immediately or implement compensating controls.
Does Spring Boot track end-of-life by point release (e.g. Spring Boot 4.1.1, Spring Boot 4.1.2)?
No — Spring Boot end-of-life dates apply to the entire 4.1.x release series, not individual point releases. A point release like Spring Boot 4.1.1 or Spring Boot 4.1.2 shares the same EOL date as Spring Boot 4.1. Security patches stop for the entire 4.1.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.
Deep Dive
Guide to Spring Boot 4.0
Spring Boot End of Life & Support Options: What To Do When Spring Boot Patches Stop (3.5 OSS Ended June 2026; 4.0 Ends December 2026)
→
Version guide
The June 30 Spring Wave: Boot 3.5, Framework 6.2, Security 6.5 & Cloud All EOL
→
Data from endoflife.date API · Generated at build time · How we source data →