Spring Boot Versions, EOL Dates, and Latest Releases (July 2026)
The current Spring Boot release, every supported branch, every end-of-life date, and what to do if you are stuck on an unsupported version. Updated for July 2026.
Spring Boot 3.5 reached open-source end of life on June 30, 2026. If you are still running 3.5 in production, see our Spring Boot 3.5 EOL migration guide for the path to 4.x, or HeroDevs Never-Ending Support for Spring to keep 3.5 patched indefinitely.
Spring Boot powers a substantial portion of the Java enterprise stack. Nearly every Java backend built in the last decade either runs on Spring Boot or shares its dependency graph through Spring Framework, Tomcat, and Jackson. With a six-month release cadence and a 12-month open-source support window, keeping production services on a supported branch is a constant moving target.
This page is the definitive reference for which Spring Boot versions are stable, which are still receiving open-source patches, and which are fully end-of-life. It is updated as new versions ship.
Latest Spring Boot Version (July 2026)
As of July 1, 2026, the current state of Spring Boot is:
- Latest stable release: Spring Boot 4.1.0, released June 10, 2026
- Latest 4.0 patch: Spring Boot 4.0.7, released June 10, 2026
- Latest 3.x release: Spring Boot 3.5.16, released June 25, 2026 (final OSS patch)
- Most recently EOL branch: Spring Boot 3.5 (OSS support ended June 30, 2026)
- Next expected release: Spring Boot 4.2, targeted for November 2026
Spring Boot 4.1 is the recommended target for new projects. Built on Spring Framework 7.0.8, it adds gRPC auto-configuration, HTTP-client SSRF mitigation, Kotlin 2.3 support, lazy datasource connections, async context propagation for @Async methods, and improved OpenTelemetry support.
How Spring Boot's Support Policy Works
Spring Boot follows a predictable open-source lifecycle managed by the Spring team. Every major and minor release moves through two phases:
- Open-source (OSS) support: 12 months of free community patches, including security fixes, bug fixes, and dependency updates published to Maven Central. Patch releases typically ship monthly during this window.
- End of Life (EOL): After the 12-month OSS window closes, the Spring team stops publishing free patches to Maven Central. The version is removed from the actively supported list.
A new minor version ships approximately every six months (roughly May and November). Spring Boot 4.1 ran slightly behind schedule, slipping from its original May 11 target to June 10, but the cadence is otherwise stable. Two minor versions are usually in OSS support at any given time. A new major version (like 4.0) ships every few years and resets the dependency baseline.
Spring Boot does not designate "LTS" releases the way Java or Node.js do. Every minor version follows the same 12-month OSS support cycle. If you need patches for a Spring Boot version after its OSS support window closes, your options are to upgrade or to adopt third-party extended support.
Complete Spring Boot Version Timeline
Spring Boot 4.1
- Initial release: June 10, 2026
- OSS support ends: July 31, 2027 (estimated, based on standard 12-month window)
- Supported Java versions: 17 through 26 (Java 21 required for jOOQ 3.20)
- Status: Current Stable
Spring Boot 4.1 is the first minor release in the 4.x line. Built on Spring Framework 7.0.8, it adds:
- gRPC auto-configuration via Spring gRPC 1.1.
- HTTP-client SSRF mitigation to harden outbound HTTP calls against server-side request forgery.
- Kotlin 2.3 support with Kotlin Serialization 1.11.
- Lazy datasource connections to reduce startup database load.
- Async context propagation for @Async methods so observability and security context flow correctly through async boundaries.
- Improved OpenTelemetry support for traces, metrics, and logs.
- Removed deprecations from 4.0, including the layertools jar mode and the -DskipTests maven flag for AOT processing of tests.
The Apache Derby integration is now deprecated following the Derby project's retirement. Teams using Derby should migrate to H2 or HSQL.
Spring Boot 4.0
- Initial release: November 20, 2025
- OSS support ends: December 31, 2026
- Latest patch: 4.0.7, released June 10, 2026
- Supported Java versions: 17 through 25
- Status: OSS Supported
Spring Boot 4.0 was the generational reset on Spring Framework 7. Headline changes:
- Java 17 minimum, Java 25 supported. Java 17 remains the floor so most existing 3.x applications can migrate without a JDK upgrade.
- Complete modularization of the Spring Boot codebase into smaller, more focused jars.
- Stable API versioning for HTTP endpoints via enhanced @HttpExchange and RestClient support.
- JSpecify null-safety annotations replace older @Nullable patterns, enabling more accurate static analysis across the Spring portfolio.
- JakartaEE 11 baseline and Jackson 3 as the new defaults.
- Removed deprecations from across the 3.x series, including older Actuator endpoints and legacy configuration properties.
Because 4.0 inherits Spring Framework 7, the migration touches Hibernate, Jackson, Tomcat, and any custom auto-configuration libraries that depend on internal Spring APIs.
Spring Boot 3.5
- Initial release: May 22, 2025
- OSS support ended: June 30, 2026
- Final OSS patch: 3.5.16, released June 25, 2026
- Supported Java versions: 17 through 25
- Status: End of Life
Spring Boot 3.5 was the final 3.x minor release and the last branch built on Spring Framework 6.2. It introduced annotation-based filter and servlet registration, auto-configuration for background bean initialization, properties for global WebClient configuration, and configuration-property binding performance improvements.
Spring Boot 3.5 reached open-source end of life on June 30, 2026. No further open-source patches will be published to Maven Central. The final OSS release, 3.5.16, shipped June 25, 2026, just five days before the EOL date.
Still running Spring Boot 3.5? HeroDevs Never-Ending Support for Spring starts the day OSS support ended (July 1, 2026) with no gap in CVE coverage. See our Spring Boot 3.5 EOL migration guide for the upgrade-vs-NES decision framework.
Spring Boot 3.4
- Initial release: November 21, 2024
- OSS support ended: December 31, 2025
- Final OSS patch: 3.4.13, released December 18, 2025
- Supported Java versions: 17 through 24
- Status: End of Life
Spring Boot 3.4 introduced structured logging in JSON format out of the box (Elastic Common Schema, GELF, Logstash), REST client interface improvements, and expanded @ServiceConnection support for additional Testcontainers modules.
As of July 2026, 3.4 has been EOL for seven months. CVEs disclosed against 3.4 must be addressed either by upgrading to 4.x or through third-party extended support.
Still running Spring Boot 3.4? Spring NES provides ongoing CVE patches and security support so you can stay compliant without an emergency migration to 4.x.
Spring Boot 3.3
- Initial release: May 23, 2024
- OSS support ended: June 30, 2025
- Final OSS patch: 3.3.13, released June 19, 2025
- Supported Java versions: 17 through 23
- Status: End of Life
Spring Boot 3.3 brought first-class virtual threads support, CDS (Class Data Sharing) integration for faster startup, Bitnami-based default container images, and Micrometer observability improvements.
Spring Boot 3.3.2 Release Date
Spring Boot 3.3.2 was released on July 18, 2024. It shipped with 50 bug fixes, documentation improvements, and dependency upgrades to Tomcat 10.1.26, Jackson 2.17.2, and Reactor 2023.0.8. The 3.3 branch is now fully end-of-life. Applications on any 3.3.x patch release, including 3.3.2, no longer receive open-source CVE fixes.
Still running Spring Boot 3.3? Spring NES keeps the 3.3 branch patched against new CVEs in Spring Framework 6.1, Tomcat, Jackson, and Hibernate.
Spring Boot 3.2
- Initial release: November 23, 2023
- OSS support ended: December 31, 2024
- Final OSS patch: 3.2.12, released November 21, 2024
- Supported Java versions: 17 through 21
- Status: End of Life
Spring Boot 3.2 was a milestone release, adding native virtual threads support, JVM checkpoint restore via CRaC, and RestClient as a replacement for RestTemplate.
Spring Boot 3.2.5 Release Date
Spring Boot 3.2.5 was released on April 18, 2024. It shipped with 46 bug fixes, documentation improvements, and dependency upgrades including Tomcat 10.1.20, Jackson 2.15.4, and Hibernate 6.4.4. Notable fixes included SSL bundle reloading and a regression in @ConfigurationProperties binding for nested records.
Like 3.3.2, Spring Boot 3.2.5 is end-of-life. The entire 3.2 branch is unsupported. Applications still running 3.2.x are exposed to CVEs in Spring Framework 6.1, Tomcat 10.1, Jackson, and transitive dependencies with no open-source patch path.
Still running Spring Boot 3.2? Spring NES covers the 3.2 branch and all transitive dependencies (Tomcat, Jackson, Hibernate, Log4j) for as long as you need.
Spring Boot 3.1
- Initial release: May 18, 2023
- OSS support ended: June 30, 2024
- Final OSS patch: 3.1.12, released May 23, 2024
- Supported Java versions: 17 through 21
- Status: End of Life
Spring Boot 3.1 introduced Docker Compose integration for local development and Spring Authorization Server 1.1. It has been fully end-of-life for over two years. Dependency CVEs accumulate monthly.
Still running Spring Boot 3.1? Spring NES provides drop-in secure replacements for 3.1.x with continued patching and compliance documentation.
Spring Boot 3.0
- Initial release: November 24, 2022
- OSS support ended: December 31, 2023
- Final OSS patch: 3.0.13, released November 23, 2023
- Supported Java versions: 17 through 21
- Status: End of Life
Spring Boot 3.0 was the first release on Spring Framework 6 and the JakartaEE namespace migration (javax.* to jakarta.*). It has been fully end-of-life since the end of 2023.
Still running Spring Boot 3.0? Spring NES keeps 3.0 patched against the growing CVE backlog in Spring Framework 6.0, Tomcat 10.1, and Hibernate 6.
Spring Boot 2.7
- Initial release: May 19, 2022
- OSS support ended: June 30, 2023
- Final OSS patch: 2.7.18, released November 23, 2023
- Supported Java versions: 8 through 21
- Status: End of Life
Spring Boot 2.7 was the final 2.x minor release and the recommended bridge for migrating applications to 3.0. Because it shipped during the 3.0 announcement period, the Spring team continued producing 2.7 patches past the standard OSS window, with the final OSS patch (2.7.18) landing in November 2023.
Despite being EOL, Spring Boot 2.7 has the largest installed base of any single Spring Boot version. Many enterprise applications are stuck on 2.7 because of:
- Java 8 or Java 11 dependencies that block the move to 3.x (which requires Java 17+).
- Third-party libraries that have not been ported to the JakartaEE namespaces.
- Custom security or auto-configuration code that depends on internal Spring APIs that changed in 3.0.
These applications are now running unpatched against a growing list of CVEs in Spring Framework 5.3, Tomcat 9, Jackson, Hibernate 5.6, and Log4j.
Still running Spring Boot 2.7? Spring NES is the established path for 2.7 environments that cannot complete the JakartaEE migration to 3.x on an audit timeline. NES covers the full transitive dependency tree, including Java 8 environments.
Spring Boot 2.6 and Earlier
All Spring Boot 2.6, 2.5, 2.4, 2.3, 2.2, 2.1, and 2.0 versions are fully end-of-life. Their OSS support windows closed years ago. These versions ship with Spring Framework 5.x and dependencies that have known, unpatched vulnerabilities in Tomcat, Jackson, Hibernate, and the JVM baseline.
Still running Spring Boot 2.6 or earlier? Spring NES covers 2.x branches all the way back to 2.0 with continued CVE patching across Spring Framework 5.x, Tomcat 9, Jackson, and Log4j.
Spring Boot 1.x
Spring Boot 1.5.x reached end-of-life on August 6, 2019. All earlier 1.x versions have been EOL for longer. Applications on 1.x rely on Spring Framework 4.x, are typically pinned to Java 7 or Java 8, and have no path forward without significant modernization work.
Still running Spring Boot 1.x? Spring NES can extend the life of 1.5.x environments while you plan a longer-term modernization path.
What Happens After Spring Boot Reaches End of Life
When a Spring Boot version exits OSS support, three concrete things change:
- CVE patches stop being published to Maven Central. Spring Framework, Tomcat, Jackson, Hibernate, Reactor, Micrometer, and dozens of other transitive dependencies continue to ship CVEs. The Spring team stops backporting fixes to EOL branches, which means your application's CVE count grows monthly even when you change nothing.
- JDK and platform compatibility erodes. Newer JDK releases occasionally break older Spring Boot versions. Newer container runtimes, Kubernetes versions, and observability tools (OpenTelemetry, Prometheus exporters) move past the integrations that EOL Spring Boot supports.
- Compliance audits flag it. SOC 2, PCI DSS, HIPAA, FedRAMP, and the EU Cyber Resilience Act all require organizations to maintain supported software. EOL Spring Boot is a documented audit finding under any of these frameworks.
Because Spring Boot pulls in a large, deeply-nested dependency tree, even one EOL Spring Boot service often shows up in vulnerability scans with twenty or more high-severity CVEs across its dependencies, none of which can be patched by simply bumping the patch version.
Compare Your Options
If you are running an EOL Spring Boot version, you have four realistic paths.
1. Migrate to Spring Boot 4.x
- Cost: 200 to 500 engineering hours per service for the 3.x to 4.x jump. Significantly more (often 1,000+ hours) for the 2.7 to 3.x JakartaEE namespace migration.
- Timeline: Weeks to months per service.
- Audit posture: Clean, on supported version.
- Best for: Teams with engineering capacity and no immediate audit pressure. See our Spring Boot 3.5 EOL migration guide for the detailed scope.
2. Self-Patch
- Cost: Ongoing internal engineering time to monitor CVEs, backport fixes, and maintain a private fork.
- Timeline: Indefinite. CVEs continue to be disclosed.
- Audit posture: Risky. Auditors expect documented patching processes, not ad-hoc fixes.
- Best for: Almost no one. Most teams underestimate the ongoing cost of maintaining a private Spring fork across the full dependency tree.
3. Get HeroDevs Never-Ending Support
- Cost: Predictable annual subscription, typically less than one engineer-month of internal work.
- Timeline: Minutes to switch over. NES coverage starts the day OSS support ends, with no gap.
- Audit posture: Clean. NES ships with FedRAMP, SOC 2, PCI DSS, and HIPAA-aligned compliance documentation.
- Best for: Teams that cannot complete a Spring Framework 7 jump (or a 2.7-to-3.x JakartaEE migration) on the timeline an audit or breach disclosure demands. Get a custom quote.
4. Accept the Risk
- Cost: Zero today, potentially massive after a breach or audit finding.
- Timeline: N/A.
- Audit posture: Failing.
- Best for: Environments that genuinely have no production impact, no compliance exposure, and no sensitive data. In other words, almost nothing real.
Quick Reference: Is My Spring Boot Version Supported?
Frequently Asked Questions
What is the latest Spring Boot version in 2026?
Spring Boot 4.1.0 is the latest stable release, published to Maven Central on June 10, 2026. The latest 4.0 patch is 4.0.7 (also June 10, 2026), and the final 3.x patch was 3.5.16 on June 25, 2026.
Is Spring Boot 4 out?
Yes. Spring Boot 4.0 was released on November 20, 2025, and Spring Boot 4.1 followed on June 10, 2026. Both are built on Spring Framework 7 and require Java 17 minimum, with support up through Java 26 in 4.1.
How many Spring Boot versions are there?
There have been 17 minor release lines across four major versions: 1.5 in 1.x, eight minors in 2.x (2.0 through 2.7), six minors in 3.x (3.0 through 3.5), and two minors in 4.x (4.0 and 4.1) as of July 2026. Only 4.0 and 4.1 are currently in open-source support.
Does Spring Boot have an LTS release?
No. Spring Boot does not designate any release as LTS. Every minor version follows the same 12-month OSS support cycle, with new minors shipping every six months. For continued patches after OSS support ends, teams rely on third-party extended support like HeroDevs NES.
Is Spring Boot 3.4.5 stable?
Yes, 3.4.5 was a stable patch on the 3.4 branch when it shipped in April 2025. But the entire 3.4.x line reached end of life on December 31, 2025, so running 3.4.5 today means running an unpatched version.
Is Spring Boot 2.7.18 compatible with Java 8?
Yes. Spring Boot 2.7.18 supports Java 8 through Java 21 and is the last Spring Boot release to support Java 8. Note that 2.7 has been EOL since June 30, 2023, so 2.7.18 receives no further patches even though it remains compatible with Java 8.
When did Spring Boot 3.5 reach end of life?
Spring Boot 3.5 reached open-source end of life on June 30, 2026. The final OSS patch, 3.5.16, was released June 25, 2026, just five days before the EOL date.
Is Spring Boot 2.7 still supported?
No. Spring Boot 2.7 reached OSS end of life on June 30, 2023. A courtesy final patch (2.7.18) was published in November 2023 to ease the 3.0 migration, but no patches have shipped since.
Is Spring Boot 3.2 still supported?
No. Spring Boot 3.2 reached OSS end of life on December 31, 2024. As of July 2026, every 3.2.x patch (including 3.2.5 and the final 3.2.12) is unsupported.
When was Spring Boot 3.3.2 released?
Spring Boot 3.3.2 was released on July 18, 2024 with 50 bug fixes and dependency upgrades to Tomcat 10.1.26, Jackson 2.17.2, and Reactor 2023.0.8. The 3.3 branch reached OSS EOL on June 30, 2025.
When was Spring Boot 3.2.5 released?
Spring Boot 3.2.5 was released on April 18, 2024 with 46 bug fixes and upgrades to Tomcat 10.1.20, Jackson 2.15.4, and Hibernate 6.4.4. The 3.2 branch is now fully end-of-life.
Where can I get Spring Boot support after end of life?
HeroDevs Never-Ending Support for Spring provides continued security patches, compliance documentation, and a private Maven registry for EOL Spring Boot versions. Coverage starts the day OSS support ends, with no gap in patching.
What is the difference between Spring Boot and Spring Framework EOL?
Spring Boot and Spring Framework are separate projects with separate lifecycles. Spring Boot 3.x runs on Spring Framework 6.x, and Spring Boot 4.x runs on Spring Framework 7.x. For Spring Framework's separate EOL schedule, see our Spring Framework end-of-life guide.
Taking Action
Spring Boot's six-month release cadence and 12-month OSS support window mean that staying current requires continuous, planned investment. Skip a single year of upgrades and you are out of open-source support. Skip two years and you are facing a major version migration (Java upgrade, JakartaEE namespace change, Spring Framework 7 dependency tree rewrite) under audit pressure.
With Spring Boot 3.5 now end-of-life as of June 30, 2026, every 3.x branch and every 2.x branch is unsupported by the upstream Spring team. Whether your path is upgrading to 4.x or adopting HeroDevs Never-Ending Support, the worst option is to do nothing and let CVE counts accumulate month over month.
If your organization is running an end-of-life version of Spring Boot, contact HeroDevs to discuss your options for continued security patching, compliance assurance, and migration planning.
Related Resources
Resources
View All Articles
.png)
.png)