Spring Framework EOL: end-of-life dates for 5.3, 6.1, 6.2 and 7.0
Spring Framework EOL dates: 5.3 lost open-source support on 31 August 2024 and 6.1 on 30 June 2025. 6.0 ended in June 2024 and 6.2 on 30 June 2026. Only Spring Framework 7.0 is in open-source support now, to 31 July 2027. Dates checked against endoflife.date and the spring.io generations data on 20 October 2026.
Spring Framework support dates follow the Spring Boot version that manages each framework line, under the Spring support policy. Open source support ended for 5.3 in August 2024 and for 6.2 in June 2026; both were the final feature branches of their generations and now get fixes only through commercial long-term support.
- Latest release
- 7.0.10
- Supported lines
- 1
- End-of-life lines
- 9
- Next end of life
- 7.0 · 31 Jul 2027
Spring Framework 5.3 and 6.1 are past open-source support
Still on Spring Framework 5.3 or 6.1?
Six CVEs rated 9.1 or 9.8 were published on 27 August 2026 against lines that had already left open-source support: five affect 5.3, five affect 6.1 and two affect 6.2. Their fixes ship only as commercial builds. The continuation page explains how patched builds work while the move to Spring Framework 7 is planned.
Who patches Spring Framework after end of life
OSSeva provides Spring Framework extended support: patched, signed builds for Spring Framework 6.2, 6.1, 6.0, 5.3 and 5.2 after upstream support ends.
Spring Framework release timeline
All Spring Framework versions, release dates and end-of-life dates
| Version | Released | OSS support | Commercial Support | Latest | OSSeva |
|---|---|---|---|---|---|
| 7.0 | 1 year ago(30 Nov 2025) | Ends in 8 months(31 Jul 2027) | Ends in 1 year and 8 months(31 Jul 2028) | 7.0.10 | – |
| 6.2 | 2 years ago(30 Nov 2024) | Ended 5 months ago(30 Jun 2026) | Ends in 5 years and 7 months(30 Jun 2032) | 6.2.19 | Patched |
| 6.1 | 3 years ago(30 Nov 2023) | Ended 1 year and 5 months ago(30 Jun 2025) | Ends in 5 years and 7 months(30 Jun 2032) | 6.1.21 | Patched |
| 6.0 | 4 years ago(30 Nov 2022) | Ended 2 years and 5 months ago(30 Jun 2024) | Ends in 5 years and 7 months(30 Jun 2032) | 6.0.23 | Patched |
| 5.3 (LTS)Spring Framework 5.3 end of life | 6 years and 1 month ago(31 Oct 2020) | Ended 2 years and 3 months ago(31 Aug 2024) | Ends in 2 years and 7 months(30 Jun 2029) | 5.3.39 | Patched |
| 5.2 | 7 years and 2 months ago(30 Sept 2019) | Ended 4 years and 11 months ago(31 Dec 2021) | Ends in 2 years and 7 months(30 Jun 2029) | 5.2.25 | Patched |
| 5.1 | 8 years and 2 months ago(30 Sept 2018) | Ended 5 years and 10 months ago(31 Dec 2020) | Ended 3 years and 11 months ago(31 Dec 2022) | 5.1.20 | – |
| 5.0 | 9 years and 2 months ago(28 Sept 2017) | Ended 5 years and 10 months ago(31 Dec 2020) | Ended | 5.0.20 | – |
| 4.3 | 10 years and 5 months ago(10 Jun 2016) | Ended 5 years and 10 months ago(31 Dec 2020) | Ended | 4.3.30 | – |
| 3.2 | 13 years and 11 months ago(13 Dec 2012) | Ended 9 years and 10 months ago(31 Dec 2016) | Ended | 3.2.18 | – |
Lifecycle data from endoflife.date (MIT licence), refreshed 15 Nov 2026. Upstream policy: github.com. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
Open-source end versus commercial end
Open-source support means the Spring team publishes public releases with fixes. Commercial support means Broadcom publishes fixes for the line only to paying subscribers, and spring.io lists the end date of each window.
Spring Framework commercial windows are long: 5.3 runs to 30 June 2029 and every 6.x line to 30 June 2032. That is why the open-source date matters more than the commercial one. Between them, the fixes exist but only paying subscribers receive them.
Spring Framework support windows. Dates checked against endoflife.date and the spring.io generations data on 20 October 2026.
| Line | Open-source support ends | Commercial support ends | Managed by Spring Boot |
|---|---|---|---|
| 7.0 | 31 Jul 2027 | 31 Jul 2028 | 4.0, 4.1 |
| 6.2 | 30 Jun 2026 | 30 Jun 2032 | 3.4, 3.5 |
| 6.1 | 30 Jun 2025 | 30 Jun 2032 | 3.2, 3.3 |
| 6.0 | 30 Jun 2024 | 30 Jun 2032 | 3.0, 3.1 |
| 5.3 | 31 Aug 2024 | 30 Jun 2029 | 2.4 to 2.7 |
Source: spring.io generations data via endoflife.date. The full table above lists every line.
CVEs since each line ended
These are the CVEs published against Spring Framework 5.3 and 6.2 since their open-source support ended, from OSSeva's CVE directory. Each has a fix, and each fix ships only as a commercial release.
Counts from the directory as of 20 October 2026 (Spring Framework 5.3: 5 since 31 Aug 2024, 5 scored 7.0 or higher; Spring Framework 6.2: 2 since 30 Jun 2026, 2 scored 7.0 or higher).
| Line | CVE | CVSS | Published | Issue | Fixed in (commercial builds only) |
|---|---|---|---|---|---|
| Spring Framework 5.3 | CVE-2026-47884 | 9.8 | 27 Aug 2026 | Use of XsltView in a Spring MVC application can result in SSRF and RCE attack if the application… | 5.3.50 |
| Spring Framework 5.3 | CVE-2026-47891 | 9.8 | 27 Aug 2026 | Spring WebFlux application that relies on the Aalto XML processor to parse XML input does not… | 5.3.50 |
| Spring Framework 5.3 | CVE-2026-47892 | 9.8 | 27 Aug 2026 | WebFlux application using functional endpoints and deployed with DispatcherServlet may be… | 5.3.50 |
| Spring Framework 5.3 | CVE-2026-59313 | 9.8 | 27 Aug 2026 | Spring MVC applications using the functional web framework are vulnerable to stream corruption… | 5.3.50 |
| Spring Framework 5.3 | CVE-2026-59283 | 9.1 | 27 Aug 2026 | Applications that evaluate Spring Expression Language (SpEL) expressions using… | 5.3.50 |
| Spring Framework 6.2 | CVE-2026-47890 | 9.8 | 27 Aug 2026 | Spring MVC and WebFlux applications are vulnerable to stream corruption when using Server-Sent… | 6.2.20 |
| Spring Framework 6.2 | CVE-2026-59313 | 9.8 | 27 Aug 2026 | Spring MVC applications using the functional web framework are vulnerable to stream corruption… | 6.2.20 |
The directory lists Spring Framework CVEs matched at NVD to the product with a CVSS score of 7.0 or higher, so it is a subset of every Spring Framework advisory. The fixed-in version is the first release above the affected range in each advisory.
Upgrade to Spring Framework 7, buy Broadcom support, or patch
Spring Framework lines follow the Spring Boot line that manages them, so the choice is the same as for Boot: move, pay Broadcom for a line still inside its commercial window, or keep the line patched while the move is planned.
| Option | What it is | It fits when | The catch |
|---|---|---|---|
| Upgrade to Spring Framework 7.0 | Usually done by moving Spring Boot from 3.5 to 4.1. Needs Java 17 or later and the Jakarta EE namespace. | The application can be retested on a new major line. | Teams on Java 8 are tied to 5.3, so the JDK and the Spring move have to happen together. |
| Buy Broadcom commercial support | A paid Spring subscription for the lines still inside their commercial window. | The estate suits Broadcom's terms. | 5.3 runs to 30 June 2029 and 6.0, 6.1 and 6.2 to 30 June 2032. Fixes such as 5.3.50 and 6.2.20 ship only to subscribers. |
| Patched builds from OSSeva | Signed, backported Spring Framework 5.3 builds scoped to named modules. | The move is planned but the audit date comes first. | A subscription for as long as you stay on the line. It buys time and does not replace the upgrade. |
Running an end-of-life Spring Framework version?
OSSeva keeps end-of-life Spring Framework patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.
Spring Framework extended supportWhen does Spring Framework 5.3 reach end of life?
Open-source support for Spring Framework 5.3 ended on 31 August 2024, and the last public release is 5.3.39. Every 5.3 patch release, including 5.3.20, shares that date. spring.io lists commercial support for 5.3 until 30 June 2029. Dates checked 20 October 2026.
When does Spring Framework 6.1 reach end of life?
Open-source support for Spring Framework 6.1 ended on 30 June 2025, and the last public release is 6.1.21. spring.io lists commercial support for 6.1 until 30 June 2032. Dates checked 20 October 2026.
When does Spring Framework 7 reach end of life?
Open-source support for Spring Framework 7.0 ends on 31 July 2027 and commercial support on 31 July 2028, per spring.io. It is the only Spring Framework line in open-source support today. Dates checked 20 October 2026.
When does Spring Framework 6.2 reach end of life?
Open-source support for Spring Framework 6.2 ended on 30 June 2026, and the last public release is 6.2.19. spring.io lists commercial support for 6.2 until 30 June 2032. Dates checked 20 October 2026.
Which Spring Framework version is in open-source support?
Only 7.0, until 31 July 2027. Every 6.x line and 5.3 have left open-source support, so fixes for them reach only Broadcom subscribers and customers of third-party providers. Dates checked 20 October 2026.
Is Spring Framework 5.3 end of life?
Open source support for Spring Framework 5.3 ended on 31 August 2024, and 5.3.39 was its last open source release. Because 5.3 was the final feature branch of the 5th generation, commercial support from Broadcom continues until 30 June 2029. The free 5.3 builds get no further CVE fixes.
Is Spring Framework 6 end of life?
Open source support for the whole 6.x generation has ended. 6.2, the final 6.x feature branch, lost it on 30 June 2026, after 6.0 in June 2024 and 6.1 in June 2025. Commercial support for all three lines runs until 30 June 2032. The open source path forward is the 7.x generation.
Which JDK does each Spring Framework version need?
Spring Framework 7.x runs on JDK 17 to 25 and later, 6.2 on JDK 17 to 25, and 5.3 on JDK 8 to 21, per the Spring Framework wiki. The Spring team fully tests on LTS JDKs, currently 17, 21 and 25. Teams still on Java 8 are tied to 5.3, which is past open source support.
What is the latest Spring Framework version?
7.0.10, released 22 Oct 2026, on the 7.0 line.
When is the next Spring Framework end of life?
Spring Framework 7.0 reaches the end of oss support on 31 Jul 2027. After that date the project stops shipping security fixes for 7.0, and CVEs disclosed later stay unpatched upstream.
Which Spring Framework versions are still supported?
7.0 (until 31 Jul 2027). Every other line has reached end of life, per the dates in the table above.
Can I get security patches for an end-of-life Spring Framework version?
Yes. OSSeva ships signed builds with backported CVE fixes for Spring Framework 6.2, 6.1, 6.0, 5.3 and 5.2 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.
Who provides Spring Framework support after end of life?
OSSeva provides Spring Framework extended support: patched, signed builds for Spring Framework 6.2, 6.1, 6.0, 5.3 and 5.2 after upstream support ends.
Get a quote
Still running an end-of-life Spring Framework?
Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.
Prefer to talk or read more first?