OSSeva Blog
OperationsWhy Spring's Open-Source and Commercial End Dates Differ, and What That Means for Your Patch Plan
Spring publishes two end dates for each line: when open-source support stops and when commercial support stops. For most Spring Boot lines the gap is 12 months; for 2.7 and 3.5, which Spring marks as extended lines, it is 72 months. On 31 December 2026 two things happen on the same day: Spring Boot 4.0 loses open-source support and Spring Boot 3.4 loses commercial support. Dates are from api.spring.io, the data behind spring.io's support tab, read 17 November 2026. If a line you run has passed its open-source date, Spring Boot extended support keeps it patched.
Running Spring Framework in production? OSSeva patches and supports it, end-of-life versions included.
Spring Framework extended support: what is coveredHow big is the gap between Spring's open-source and commercial end dates?
The gap is 12 months on 8 of the 11 Spring Boot lines from 2.6 onward, 15 months on 2.6, and 72 months on 2.7 and 3.5.
| Spring Boot line | Open-source support ends | Commercial support ends | Gap |
|---|---|---|---|
| 2.6 | 30 Nov 2022 | 29 Feb 2024 | 15 months |
| 2.7 (extended) | 30 Jun 2023 | 30 Jun 2029 | 72 months |
| 3.0 | 31 Dec 2023 | 31 Dec 2024 | 12 months |
| 3.1 | 30 Jun 2024 | 30 Jun 2025 | 12 months |
| 3.2 | 31 Dec 2024 | 31 Dec 2025 | 12 months |
| 3.3 | 30 Jun 2025 | 30 Jun 2026 | 12 months |
| 3.4 | 31 Dec 2025 | 31 Dec 2026 | 12 months |
| 3.5 (extended) | 30 Jun 2026 | 30 Jun 2032 | 72 months |
| 4.0 | 31 Dec 2026 | 31 Dec 2027 | 12 months |
| 4.1 | 31 Jul 2027 | 31 Jul 2028 | 12 months |
| 4.2 | 31 Dec 2027 | 31 Dec 2028 | 12 months |
The gap is OSSeva's count of months between the two dates on api.spring.io. The Spring Boot generations list marks 2.7.x and 3.5.x as "extended"; no other line carries that mark. The full list is on Spring Boot EOL dates.
Why do the dates for one application stack differ?
Because Boot, Framework and Security each have their own calendar, and the dates can disagree inside a single application. Spring Boot 3.4 runs on Spring Framework 6.2, which needs 6.2.15 or above per the Boot 3.4.13 requirements page. Boot 3.4's commercial support ends on 31 December 2026, while Spring lists commercial support for Framework 6.0, 6.1 and 6.2 to 30 June 2032. Spring Security 6.4 follows Boot 3.4 to 31 December 2026, and Security 6.5 runs to 30 June 2032. A scanner flags the layer with the earliest date, so list all three.
| Layer | Open-source ended | Commercial ends |
|---|---|---|
| Spring Boot 3.4 | 31 Dec 2025 | 31 Dec 2026 |
| Spring Framework 6.2 (under Boot 3.4 and 3.5) | 30 Jun 2026 | 30 Jun 2032 |
| Spring Security 6.4 | 31 Dec 2025 | 31 Dec 2026 |
| Spring Framework 5.3 (under Boot 2.7) | 31 Aug 2024 | 30 Jun 2029 |
What does that mean for your patch plan?
Plan to the earliest date in the stack, and treat a commercial date as the end of a fix stream you pay for.
- List Boot, Framework and Security versions per service. Use the resolved versions in the dependency tree, not the Boot version alone.
- Mark each line open-source, commercial-only or ended. After the open-source date, fixes exist only as commercial releases or third-party backports.
- Act on 31 December 2026. Boot 4.0 services can move to 4.1, which has open-source support to 31 July 2027. Boot 3.4 services lose commercial support that day and have no open-source fix path.
- Pick a destination per service. Boot 4.1 is the longest open-source target; 3.5 has the longest commercial window, to 2032, but left open-source support on 30 June 2026.
- Cover the gap with a dated route. Spring Enterprise from Broadcom for lines inside its window, or third-party patched builds for the rest.
Which Spring lines need action first?
Boot 3.4 and Boot 4.0 have a deadline on 31 December 2026; Boot 2.7 and Boot 3.5 do not, because their commercial windows run to 2029 and 2032. Boot 3.0 to 3.3 have already lost commercial support, so any service on them has no vendor fix stream from Spring. See the Spring Boot 4.0 end of support checklist and the Spring Boot 3.4 end of support checklist. For the vendors that cover the gap, see Spring Boot support after open-source end of life.
OSSeva ships patched builds for the lines that have left open-source support, Boot 2.6, 2.7 and 3.0 to 3.5, with Critical CVEs patched within 48 hours and High within 7 days; Spring Boot extended support lists the lines and the Spring projects covered.
Frequently asked questions
When does Spring Boot 4.0 lose open-source support?
On 31 December 2026. Commercial support runs to 31 December 2027. Spring Boot 4.1 has open-source support to 31 July 2027.
When does Spring Boot 3.4 lose commercial support?
On 31 December 2026. Its open-source support ended on 31 December 2025, and the last public release is 3.4.13.
Why does Spring Boot 2.7 have a 2029 date?
api.spring.io marks 2.7.x as an extended line with commercial support to 30 June 2029, six years after open-source support ended on 30 June 2023. The endpoint gives the dates, not the reasons.
Is commercial support the same as open-source support?
No. After the open-source date, fixes are released only to paying customers or backported by third parties. The public releases stop.
Tags
Related articles
Who Provides Spring Boot and Spring Framework Support After Open Source End of Life?
October 6, 2026OperationsSpring Support Calendar 2026 to 2027: Every Spring Boot, Framework and Security Deadline
October 5, 2026OperationsSpring Boot Commercial Support: What to Check Beyond Spring Enterprise
November 17, 2026MigrationSpring Boot 2.7 on Java 8: what is still supported, and until when
November 15, 2026OperationsWhich JDK Vendor Still Patches Java 8, 11 and 17? Vendor-by-Vendor Dates
November 17, 2026OperationsPatching the Whole Stack: Spring, Tomcat and Java 8 After EOL
November 17, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?