Spring Boot Versions, EOL Dates, and Latest Releases (April 2026)

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 (April 2026)

As of April 20, 2026, the current state of Spring Boot is:

• Latest stable release: Spring Boot 4.0.5, released March 26, 2026
• Latest Spring Boot 3.x release: Spring Boot 3.5.11, released February 19, 2026
• Current GA branch: Spring Boot 4.0.x (initial release November 20, 2025)
• Next expected release: Spring Boot 4.1, targeted for May 2026 (currently in milestone builds, latest 4.1.0-M4)
• Most recently EOL branch: Spring Boot 3.4 (OSS support ended December 31, 2025)

Spring Boot 4.0 is the recommended target for new projects. It is built on Spring Framework 7, requires Java 17 as a minimum, adds first-class Java 25 support, introduces stable API versioning for HTTP endpoints, modularizes the Spring Boot codebase into smaller jars, and replaces older null-safety annotations with JSpecify.

‍

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:

1. 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.
2. 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), which means 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, typically with a new Spring Framework major version underneath.

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.0

• Initial release: November 20, 2025
• OSS support ends: December 31, 2026
• Latest patch (April 2026): 4.0.5, released March 26, 2026
• Supported Java versions: 17 through 25
• Status: Current GA

Spring Boot 4.0 is the first major release on the Spring Framework 7 baseline. 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.
• Removed deprecations from across the 3.x series, including older Actuator endpoints and legacy configuration properties. Check the official migration guide before upgrading.

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 ends: June 30, 2026
• Latest patch (April 2026): 3.5.11, released February 19, 2026
• Supported Java versions: 17 through 25
• Status: OSS Supported (last 3.x minor)

Spring Boot 3.5 is the final 3.x minor release. It is the recommended branch for teams that need to stay on Spring Framework 6 for compatibility reasons: older application servers, legacy library constraints, or codebases that are not yet ready to absorb the Spring Framework 7 dependency changes.

Notable 3.5 additions include annotation-based filter and servlet registration, auto-configuration for background bean initialization, properties for global WebClient configuration, and configuration-property binding performance improvements.

Patch releases will continue through OSS until June 30, 2026. If you are running 3.5 today, your migration decision is whether to move sideways to 4.0 before that date or extend the 3.5 lifeline through third-party extended support.

‍

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 April 2026, 3.4 receives no open-source patches. CVEs disclosed against 3.4 must be addressed either by upgrading to 3.5 or 4.0 or through third-party extended support like HeroDevs Never-Ending Support for Spring Boot.

‍

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. At time of release it was the second patch on the 3.3 branch, addressing regressions reported after 3.3.0 and 3.3.1.

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.

‍

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 (including 3.2.5, 3.2.12, or any other patch) are exposed to CVEs in Spring Framework 6.0, Tomcat 10.1, Jackson, and transitive dependencies with no open-source patch path.

‍

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 nearly two years. Dependency CVEs accumulate monthly.

‍

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.

‍

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.

‍

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.

‍

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.

‍

What Happens After Spring Boot Reaches End of Life

When a Spring Boot version exits OSS support, three concrete things change:

1. 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.
2. 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.
3. 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.

‍

Options if You Are Running an EOL Spring Boot Version

There are two realistic paths.

1. Upgrade to a Supported Version

The official guidance and the lowest long-term cost. The migration cost depends on how far behind you are:

• 3.x to 4.0: Usually a few days of work per service. Java 17 baseline must be in place, and JSpecify annotations may surface latent null-safety issues. Spring Framework 7 dependency updates touch Hibernate, Jackson, and Tomcat.
• 3.0/3.1/3.2/3.3/3.4 to 3.5 or 4.0: Typically straightforward, with mostly dependency updates and minor configuration property renames.
• 2.7 to 3.x: This is the painful jump. Requires Java 17, the JakartaEE namespace migration (javax.* to jakarta.*), Spring Security 6 changes, and verification of every third-party dependency for Jakarta compatibility.
• 2.x older than 2.7: Upgrade to 2.7 first, then make the 3.x jump.

The Spring team maintains official migration guides for each major version transition.

2. Adopt HeroDevs Never-Ending Support

HeroDevs Never-Ending Support (NES) for Spring provides drop-in secure replacements that begin the day your OSS support ends. There is no gap: when Spring's open-source patches stop, HeroDevs picks up with continued CVE patching, compliance documentation (FedRAMP, SOC 2, PCI DSS), and a private Maven registry.

NES covers Spring Boot 3.2, 3.3, 3.4, and older branches, plus Spring Framework 5.x, Spring Security, and the full transitive dependency tree (Tomcat, Jackson, Hibernate, Log4j). It is built by engineers with deep Spring expertise and is the pragmatic option for teams that cannot complete the 2.7-to-3.x migration, or a major Spring Framework 7 jump, on the timeline an audit or breach disclosure demands.

For a deeper look at what NES covers for the most recent EOL branches, see the announcement: Never-Ending Support Now Covers Spring Boot 3.2, 3.3 and 3.4.

‍

Quick Reference: Is My Spring Boot Version Supported?

‍

Frequently Asked Questions

What is the latest Spring Boot version in 2026?

As of April 20, 2026, the latest stable Spring Boot release is 4.0.5, published to Maven Central on March 26, 2026. The latest 3.x release is Spring Boot 3.5.11, released February 19, 2026. Spring Boot 4.1 is expected in May 2026 and is currently available in milestone form as 4.1.0-M4.

What is the latest Spring Boot version in April 2026?

Spring Boot 4.0.5 is the latest stable release as of April 2026. The Spring team ships patch releases roughly monthly, so a 4.0.6 is likely in the near future.

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.

When does Spring Boot 3.5 reach end of life?

Spring Boot 3.5 OSS support ends June 30, 2026. After that date, no open-source patches will be published to Maven Central. Teams that need continued patches for 3.5 after June 30, 2026 should either upgrade to 4.0 or adopt HeroDevs Never-Ending Support.

Is Spring Boot 2.7 still supported?

No. Spring Boot 2.7 reached the end of OSS support on June 30, 2023 (with a final patch, 2.7.18, published in November 2023 to smooth the 3.0 migration). It is fully end-of-life and receives no open-source patches. Applications still running on 2.7 should either migrate to 3.5/4.0 or adopt extended support.

Is Spring Boot 3.2 still supported?

No. Spring Boot 3.2 reached end of OSS support on December 31, 2024. As of April 2026, it has been end-of-life for over 15 months. All 3.2.x patch versions (including 3.2.5 and the final 3.2.12) are unsupported.

When was Spring Boot 3.3.2 released?

Spring Boot 3.3.2 was released on July 18, 2024. It shipped 50 bug fixes and dependency upgrades, including 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. It included 46 bug fixes and dependency upgrades to Tomcat 10.1.20, Jackson 2.15.4, and Hibernate 6.4.4, plus fixes for SSL bundle reloading and @ConfigurationProperties binding for nested records. 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 Spring Boot versions past their OSS end-of-life date. HeroDevs 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.

Whether your path is upgrading to 4.0 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.