Spring Framework End of Life Dates
framework
Developers rely on the Spring Framework to build robust and scalable applications, and for good reason - it has been a cornerstone of the Java ecosystem since its creation in 2004. The Spring Framework is maintained by VMware, which ensures that the framework stays up-to-date with the latest security patches and features. By tracking the end-of-life dates of each Spring Framework release, developers can plan their upgrades and migrations to ensure that their applications remain secure and supported. With a total of 10 versions released to date, it can be challenging to keep track of which versions are still supported and which have reached the end of their life cycle.
The end-of-life landscape for the Spring Framework is characterized by a large number of retired versions, with 8 out of 10 versions no longer supported. Currently, only 2 versions are still actively supported, with the latest stable version being 6.2.19. The next version to reach end-of-life is 6.2, which is scheduled to expire on 2026-06-30. This means that developers who are still using version 6.2 will need to upgrade to a newer version before this date to ensure that they continue to receive security patches and support. The last version to reach end-of-life was 6.1, which expired on 2025-06-30.
Fortunately, the Spring Framework has an excellent security track record, with a total of 0 CVEs tracked and 0 critical CVEs reported. As a result, there is no most affected version, and the framework is not listed on the Known Exploited Vulnerabilities catalog. Despite this, developers should still prioritize upgrading to the latest supported version to ensure that they have access to the latest security patches and features. By staying on top of the end-of-life dates and security patch timelines for the Spring Framework, developers can ensure that their applications remain secure, stable, and supported.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 7.0 | Nov 30, 2025 | — | Jul 31, 2027 | in 372d | 7.0.8 | — | Active | |
| 6.2 | Nov 30, 2024 | — | Jun 30, 2026 | 24d ago | 6.2.19 | — | EOL | |
| 6.1 | Nov 30, 2023 | — | Jun 30, 2025 | 389d ago | 6.1.21 | — | EOL | |
| 6.0 | Nov 30, 2022 | — | Jun 30, 2024 | 754d ago | 6.0.23 | — | EOL | |
| 5.3 LTS | Oct 31, 2020 | — | Aug 31, 2024 | 692d ago | 5.3.39 | — | EOL | |
| 5.2 | Sep 30, 2019 | — | Dec 31, 2021 | 1666d ago | 5.2.25 | — | EOL | |
| 5.1 | Sep 30, 2018 | — | Dec 31, 2020 | 2031d ago | 5.1.20 | — | EOL | |
| 5.0 | Sep 28, 2017 | — | Dec 31, 2020 | 2031d ago | 5.0.20 | — | EOL | |
| 4.3 | Jun 10, 2016 | — | Dec 31, 2020 | 2031d ago | 4.3.30 | — | EOL | |
| 3.2 | Dec 13, 2012 | — | Dec 31, 2016 | 3492d ago | 3.2.18 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
