Spring Boot End of Life (EOL) Dates and End of Support (EOS) Dates
Spring Boot end of life (EOL) and end of support (EOS) dates: 15 Spring Boot versions have reached EOL, including Spring Boot 3.5 (EOL date: Jun 30, 2026) — no longer receiving security updates or patches. Spring Boot 4.0 reaches its End of Support date on Dec 31, 2026 — plan your upgrade path now. Spring Boot 4.1.3 is the current supported release, with support through Jul 31, 2027. Also see Apache Grails Framework end of life dates for related end-of-life information.
Currently Supported Spring Boot Releases - Active EOS/EOSL Support (1)
| Release | Supported Java Versions | Released | OSS support | Commercial Support | Latest |
|---|---|---|---|---|---|
| 4.1 | 17 - 26 | (4 months ago) | (in 8 months) | (in 1 year and 8 months) | 4.1.3 (2 days ago) |
Spring Boot Releases Nearing End of Life - Support Ending Soon (1)
| Release | Supported Java Versions | Released | OSS support | Commercial Support | Latest |
|---|---|---|---|---|---|
| 4.0 | 17 - 25 | (11 months ago) | (in 1 month and 1 week) | (in 1 year and 1 month) | 4.0.10 (2 days ago) |
Spring Boot End of Life (EOL) Releases - No Longer Supported (15)
| Release | Supported Java Versions | Released | OSS support | Commercial Support | Latest |
|---|---|---|---|---|---|
| 3.5 | 17 - 25 | (1 year and 5 months ago) | (4 months ago) | (in 5 years and 7 months) | 3.5.16 (4 months ago) |
| 3.4 | 17 - 24 | (1 year and 11 months ago) | (10 months ago) | (in 1 month and 1 week) | 3.4.13 (11 months ago) |
| 3.3 | 17 - 23 | (2 years and 5 months ago) | (1 year and 4 months ago) | (4 months ago) | 3.3.13 (1 year and 5 months ago) |
| 3.2 | 17 - 21 | (2 years and 11 months ago) | (1 year and 10 months ago) | (10 months ago) | 3.2.12 (2 years ago) |
| 3.1 | 17 - 21 | (3 years and 5 months ago) | (2 years and 4 months ago) | (1 year and 4 months ago) | 3.1.12 (2 years and 5 months ago) |
| 3.0 | 17 - 21 | (3 years and 11 months ago) | (2 years and 10 months ago) | (1 year and 10 months ago) | 3.0.13 (2 years and 11 months ago) |
| 2.7 | 8 - 21 | (4 years and 5 months ago) | (3 years and 4 months ago) | (in 2 years and 7 months) | 2.7.18 (2 years and 11 months ago) |
| 2.6 | 8 - 19 | (5 years ago) | (3 years and 11 months ago) | (2 years and 8 months ago) | 2.6.15 (3 years and 6 months ago) |
| 2.5 | 8 - 18 | (5 years and 6 months ago) | (4 years and 6 months ago) | (3 years and 2 months ago) | 2.5.15 (3 years and 6 months ago) |
| 2.4 | 8 - 16 | (6 years ago) | (5 years ago) | (3 years and 8 months ago) | 2.4.13 (5 years ago) |
| 2.3 | 8 - 15 | (6 years and 6 months ago) | (5 years and 6 months ago) | (4 years and 3 months ago) | 2.3.12 (5 years and 5 months ago) |
| 2.2 | 8 - 15 | (7 years and 1 month ago) | (6 years and 1 month ago) | (4 years and 10 months ago) | 2.2.13 (5 years and 10 months ago) |
| 2.1 | 8 - 12 | (8 years ago) | (7 years ago) | (5 years and 9 months ago) | 2.1.18 (6 years ago) |
| 2.0 | 8 - 9 | (8 years and 8 months ago) | (7 years and 8 months ago) | (6 years and 5 months ago) | 2.0.9 (7 years and 7 months ago) |
| 1.5 | 6 - 8 | (9 years and 9 months ago) | (7 years and 3 months ago) | (6 years ago) | 1.5.22 (7 years and 3 months ago) |
If you run Java services, the Spring Boot end of life calendar decides when free fixes stop reaching your code. Every 3.x branch has already left open-source maintenance, and 4.0 follows on 31 December 2026, so check your version against the table below before your next release.
Spring Boot End of Life Dates for Every Version
Each Spring line gets 12 months of OSS support and then reaches EOL. Paid commercial support stretches the calendar further for some branches. The table shows the dates endoflife.date lists as of 23 October 2026.
| Line | Initial release | OSS support ends | Commercial support ends |
|---|---|---|---|
| 4.1 | June 2026 | 31 July 2027 | 31 July 2028 |
| 4.0 | November 2025 | 31 December 2026 | 31 December 2027 |
| 3.5 | May 2025 | 30 June 2026 | 30 June 2032 |
| 3.4 | November 2024 | 31 December 2025 | 31 December 2026 |
| 3.3 | May 2024 | 30 June 2025 | 30 June 2026 |
| 2.7 | May 2022 | 30 June 2023 | 30 June 2029 |
Only 4.1 and 4.0 still receive community fixes. The 3.5 branch ended on 30 June 2026 with 3.5.16 as its final build, so Spring Boot 3.5 now sits beside 3.4 and 3.3 as unsupported.
Release Date Pattern Behind the Version Timeline
A new minor version lands roughly every six months, in May and November, so each release date gives you its EOL date almost mechanically: 12 months later, rounded to the end of June or December. Line 2.7 is the exception, with paid coverage from Tanzu running to 2029.
How the Spring Boot Support Policy and Support Window Work
The Spring team publishes its support policy openly: every major and minor release gets a 12-month OSS support window maintained for the open-source community, and patch releases usually ship monthly. They carry security fixes, bug fixes and dependency updates, published to Maven Central as free patches.
Spring Boot has no LTS label the way Java does. Each version follows the same cycle, so a release cadence of two minor lines a year means two branches are normally in OSS support at once. A major version, such as 4.0, resets the baseline every few years.
Latest Spring Boot Versions and Release Cadence
As of late October 2026, Spring Boot 4.1 is the current line, at patch 4.1.2, and Spring Boot 4.0 trails it with 4.0.9 as its newest patch. The 4.1 line, built on Spring Framework 7, adds gRPC auto-configuration, lazy datasource connections and Kotlin 2.3 support, and its OSS support runs to 31 July 2027. For a new project, start.spring.io generates a 4.1 skeleton in seconds.
What EOL Means for Your Apps and Support
EOL does not break anything on the day it arrives. Maven Central never removes a published artifact, so your Spring Boot build keeps resolving the same jars and your CI stays green. Developers often miss it for that reason. What end-of-life removes is the stream of fixes: 3.5.16 is the last 3.5 build you will get, and there is no 3.5.17.
Once a branch reaches end of life, a CVE fix lands only in supported releases. Spring Framework, Tomcat and Jackson keep shipping CVEs, and the Spring team stops backporting them, so your transitive dependencies keep accumulating issues and the vulnerability count in your scans grows even when your Spring code never changes. Auditors treat that as a finding under SOC 2, PCI DSS and similar compliance frameworks, which expect you to run supported software.
Why Unsupported Spring Boot 3.5 Apps Face More Risk
Spring Boot 3.5 reached end of life on 30 June 2026, and the timing makes that gap more dangerous this year. In April 2026 the Spring team received 482 security reports across 65 scanned projects, against a historical average of about 6.5 a month, and it produced 26 new CVEs. Most reports were medium or low severity, so the volume, not any single vulnerability, is the story.
Put that next to an end-of-life branch that no longer receives security patches and you have a plan to get paged. The Spring Boot 3.5 line, with Spring Framework 6.2 underneath, keeps its risk while discovery speeds up, which for a production service is the strongest argument for moving now.
Java Compatibility and the Spring Boot 2.7 Baseline
Java compatibility is where upgrades get blocked. Spring Boot 2.7 still runs on Java 8 through Java 21, while every 3.x and 4.x line needs Java 17 or newer: 4.1 supports Java 17 to Java 26, and 4.0 and 3.5 reach Java 25. If your service is pinned to Java 8 or 11, the JDK move comes before any Spring step.
The namespace change is the other 2.7 blocker. Moving to 3.0 forced every javax import to become jakarta, and Spring Boot 4 now sits on a Jakarta EE 11 baseline, so third-party Spring libraries must catch up.
Upgrade Path to Spring Boot 4.1 Before 4.0 Support Ends
For most teams the answer is to move straight to 4.1, not 4.0. The 4.0 line loses OSS support on 31 December 2026, so stopping there means repeating the migration within weeks, while 4.1 buys you until July 2027. The Java baseline stays at 17, so unlike the 2.7 to 3.0 jump, no forced JDK change hides in this upgrade path.
Plan the upgrade in three passes:
- Move to the latest 3.5 patch, 3.5.16, and clear every deprecation warning.
- Check your Hibernate, Jackson and Tomcat versions, since Spring Framework 7 changes the dependency layer, and replace removed Actuator endpoints.
- Switch to 4.1 and run the full test suite before you promote it to production.
The official migration guide covers property renames and removed modules. HeroDevs estimates 200 to 500 engineering hours per service for a 3.x to 4.x move.
Extended Support After End of OSS Support
If you cannot upgrade yet, extended support keeps a branch patched. VMware sells Tanzu enterprise support, and the table above shows its dates. HeroDevs Never-Ending Support for Spring is the third-party route, covering Spring Framework 5.3 and 6.x CVEs, and begins the day the end of OSS support passes, so CVE coverage has no gap. Your realistic options are:
- Migrate to a supported release.
- Self-patch with a private fork, which rarely pays off.
- Buy paid cover for the Spring Boot branch you run.
- Run unpatched and accept the exposure.
Key Takeaways on the Support Timeline
- Only 4.1 and 4.0 receive free patches, and 4.0 ends on 31 December 2026.
- EOL stops fixes, not builds, so nothing warns you.
- Check the Spring version timeline once a quarter and plan every upgrade a release ahead.