Spring Cloud End of Life Dates
other
Developers rely on Spring Cloud to build and deploy scalable, secure applications, and for good reason - the framework has been a staple of the development community since its creation. Maintained by the team at VMware, Spring Cloud has evolved over time to meet the changing needs of its users, providing a robust set of tools for building cloud-native applications. With a focus on simplicity and flexibility, Spring Cloud has become an essential component of many development projects, allowing teams to focus on writing code rather than managing infrastructure.
The end-of-life landscape for Spring Cloud is characterized by a total of 7 versions, with 5 of these having already reached the end of their supported lifespan. Currently, only 2 versions remain active, with the latest stable version being 2025.0.3. Looking ahead, the next version to reach end-of-life will be 2025.0, which is scheduled to expire on June 30, 2026. This gives developers a clear timeline to plan their upgrades and migrations, ensuring that they can continue to receive support and security patches for their applications. The most recent version to reach end-of-life was 2024.0, which expired on December 31, 2025.
From a security perspective, Spring Cloud has a clean bill of health, with a total of 0 CVEs tracked and no critical vulnerabilities reported. As a result, there is no most affected version to speak of, and the project is not subject to any known exploits. Given this positive security posture, developers can continue to use Spring Cloud with confidence, knowing that their applications are not exposed to any known vulnerabilities. To maintain this level of security, developers should continue to monitor the project's support timeline and plan their upgrades accordingly, ensuring that they remain on a supported version and can receive any necessary security patches.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2025.1 | Nov 24, 2025 | — | Jul 31, 2027 | in 372d | 2025.1.2 | — | Active | |
| 2025.0 | May 29, 2025 | — | Jun 30, 2026 | 24d ago | 2025.0.3 | — | EOL | |
| 2024.0 | Dec 3, 2024 | — | Dec 31, 2025 | 205d ago | 2024.0.3 | — | EOL | |
| 2023.0 | Dec 6, 2023 | — | Jun 30, 2025 | 389d ago | 2023.0.6 | — | EOL | |
| 2022.0 | Dec 16, 2022 | — | Jun 30, 2024 | 754d ago | 2022.0.5 | — | EOL | |
| 2021.0 | Dec 1, 2021 | — | Jun 30, 2023 | 1120d ago | 2021.0.9 | — | EOL | |
| 2020.0 | Dec 22, 2020 | — | May 31, 2022 | 1515d ago | 2020.0.6 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
