Spring Boot · Lifecycle Status

Spring Boot End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Spring Boot versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Spring Boot 3.5 reaches end of life on June 30, 2026. Plan your migration now — 52 days remaining.
Latest Active
4.0.6
4.0 series
Next EOL
3.5
Jun 30, 2026
Active Versions
1
of 16 total
EOL Versions
14
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 201720182019202020212022202320242025202620271.52.02.12.22.32.42.52.62.73.03.13.23.33.43.54.0TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.5 1.5.22 Jan 30, 2017 Aug 6, 2019 2468 days past EOL EOL
2.0 2.0.9 Mar 1, 2018 Mar 1, 2019 2626 days past EOL EOL
2.1 2.1.18 Oct 30, 2018 Oct 30, 2019 2383 days past EOL EOL
2.2 2.2.13 Oct 16, 2019 Oct 16, 2020 2031 days past EOL EOL
2.3 2.3.12 May 15, 2020 May 20, 2021 1815 days past EOL EOL
2.4 2.4.13 Nov 12, 2020 Nov 18, 2021 1633 days past EOL EOL
2.5 2.5.15 May 20, 2021 May 19, 2022 1451 days past EOL EOL
2.6 2.6.15 Nov 17, 2021 Nov 24, 2022 1262 days past EOL EOL
2.7 2.7.18 May 31, 2022 Jun 30, 2023 1044 days past EOL EOL
3.0 3.0.13 Nov 24, 2022 Dec 31, 2023 860 days past EOL EOL
3.1 3.1.12 May 31, 2023 Jun 30, 2024 678 days past EOL EOL
3.2 3.2.12 Nov 30, 2023 Dec 31, 2024 494 days past EOL EOL
3.3 3.3.13 May 31, 2024 Jun 30, 2025 313 days past EOL EOL
3.4 3.4.13 Nov 30, 2024 Dec 31, 2025 129 days past EOL EOL
3.5 3.5.14 May 31, 2025 Jun 30, 2026 52 days remaining Warning
4.0 4.0.6 Nov 30, 2025 Dec 31, 2026 236 days remaining Active

What does Spring Boot end of life mean for your organization?

When a Spring Boot version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Spring Boot should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Spring Boot?
The next Spring Boot version reaching EOL is 3.5 on June 30, 2026. See the full table above for all version EOL dates.
What is the latest supported version of Spring Boot?
The latest active version of Spring Boot is 4.0.6. Always verify against the table above as support windows can change.
What happens when Spring Boot reaches end of life?
When Spring Boot reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Spring Boot?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Spring Boot versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →