Spring Boot End of Life Dates

Developers rely on Spring Boot to simplify the process of building and deploying applications, and for good reason - it was first introduced in 2009 as a way to streamline the development process for Java-based applications, and is now maintained by VMware. Since its inception, Spring Boot has become a staple in the development community, with many using it to build a wide range of applications, from simple web services to complex enterprise systems. The ability to track end-of-life dates, supported versions, and security patch timelines is crucial for developers who want to ensure their applications remain secure and up-to-date.

The end-of-life landscape for Spring Boot is complex, with a total of 17 versions having been released over the years. Of these, 14 versions are no longer supported, while 3 remain active. The latest stable version, 3.5.15, is the current standard, but developers should be aware that version 3.5 is set to reach its end-of-life on 2026-06-30. This means that any applications still using version 3.5 will need to be upgraded to a newer version in order to continue receiving support and security patches. The last version to reach its end-of-life was 3.4, which ceased to be supported on 2025-12-31.

Fortunately, the security picture for Spring Boot is relatively clean, with no known CVEs currently tracked. This means that there are no critical vulnerabilities that developers need to be concerned about, and no versions are considered to be high-risk. As a result, developers can focus on planning their upgrades and migrations without the added pressure of addressing potential security issues. To ensure the continued security and stability of their applications, developers should prioritize upgrading to the latest supported version of Spring Boot, and stay informed about any future end-of-life dates or security patches that may be released.