Spring Security 6.4 end of life
Spring Security 6.4 left open source support on 31 December 2025. Broadcom's commercial support for it ends on 31 December 2026, per spring.io. The last open source release is 6.4.13, which Spring Boot 3.4.13 manages. Later 6.4 releases, including the fixes for two critical 2026 advisories, are Enterprise Support Only.
What now
Which vendors provide Spring Security 6.4 security patches now that support has ended?
Spring Boot Extended Support for 2.x and Spring Framework 5- End of life
- 31 December 2025 (open source); 31 December 2026 (commercial)
- Released
- Nov 2024
- Final release
- 6.4.13 (last open source release, 17 November 2025)
- Successor
- Spring Security 7.1, with Spring Boot 4.1
Date published by Spring Security support policy. We do not publish a lifecycle date we cannot source. Dates checked against the spring.io Spring Security support tab, the generations data behind it and Spring's advisories on 13 November 2026.
Last reviewed
Spring Security versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Spring Security 7.0 | 17 Nov 2025 | 31 December 2026 | Approaching |
| Spring Security 6.4 (this page) | 18 Nov 2024 | 31 December 2025 (open source); 31 December 2026 (commercial) | End of life |
| Spring Security 5.8 | 30 Nov 2022 | 31 December 2023 | End of life |
| Spring Security 6 | 21 Nov 2022 | 30 June 2026 | End of life |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 31 December 2025
- Open source 6.4.x releases, already stopped. 6.4.13 is the last one on Maven Central.
- Commercial 6.4 releases, on 31 December 2026. After that date Broadcom ships no fixes for 6.4.
- The Spring Boot line that manages it. Boot 3.4 reaches the same commercial date, and Spring Framework 6.2 under both continues to 30 June 2032.
What actually breaks in the upgrade
Security moves with Boot
Spring Boot 3.4 manages Spring Security 6.4, 3.5 manages 6.5, 4.0 manages 7.0 and 4.1 manages 7.1. Most applications take the Security version their Boot release manages, so the practical upgrade is a Spring Boot upgrade.
6.5 is a step, not a destination
Spring Security 6.5 left open source support on 30 June 2026, so moving 6.4 to 6.5 restores no open source fixes. Its value is commercial: spring.io lists it to 30 June 2032. For open source fixes the target is 7.1, supported to 31 July 2027, which arrives with Spring Boot 4.1.
Check the two critical advisories before you decide
CVE-2026-22732 reaches any 6.4 application that writes its own response headers, and the advisory gives a workaround with side effects. CVE-2026-59270 reaches only applications that use the embedded UnboundID LDAP server. Both fixes for 6.4 are Enterprise Support Only, so a team without a subscription needs a different route to them.
Authentication code is the slow part of a Boot upgrade
Security configuration is the code that stays closest to its tests and its edge cases. Budget a regression cycle for login, token, session and method-security paths, not just a compile. Spring Boot 3.4 end of support checklist.
Which Spring Security lines are supported, and until when?
Spring Security has two dates per line: when public fixes stop (open source) and when Broadcom stops shipping fixes to paying Spring Enterprise customers. 6.4 has already passed the first and reaches the second on 31 December 2026.
| Line | Open source support ends | Commercial support ends | Managed by Spring Boot |
|---|---|---|---|
| 6.3.x | 30 Jun 2025 (ended) | 30 Jun 2026 (ended) | 3.3 (ended) |
| 6.4.x | 31 Dec 2025 (ended) | 31 Dec 2026 | 3.4 |
| 6.5.x | 30 Jun 2026 (ended) | 30 Jun 2032 | 3.5 |
| 7.0.x | 31 Dec 2026 | 31 Dec 2027 | 4.0 |
| 7.1.x | 31 Jul 2027 | 31 Jul 2028 | 4.1 |
Source: the Spring Security support tab on spring.io and the generations data behind it, checked 13 November 2026. The Spring Boot column comes from the dependency versions each Boot release publishes on Maven Central (3.4.13 manages 6.4.13, 3.5.16 manages 6.5.11, 4.0.9 manages 7.0.8, 4.1.2 manages 7.1.2).
Which 2026 Spring Security advisories reach 6.4?
Two of the 2026 advisories are rated critical and name 6.4. CVE-2026-22732 (19 March 2026): when an application sets some HTTP response headers itself, Spring Security's own headers may not be written, which can expose sensitive data through caching. It affects 6.4.0 to 6.4.14, and the 6.4 fix, 6.4.15, is Enterprise Support Only. The advisory's workaround is to set HeaderWriterFilter.shouldWriteHeadersEagerly to true, which changes how headers are written.
CVE-2026-59270 (20 August 2026): the embedded UnboundID LDAP server, UnboundIdContainer, registers a well-known administrative bind DN and listens on all network interfaces. It matters only if the application uses that container, directly or through Spring Boot auto-configuration. It affects 6.4.0 to 6.4.18, and the 6.4 fix, 6.4.19, is Enterprise Support Only. 6.5.12 is also Enterprise Support Only; 7.0.7 and 7.1.1 are open source.
Source: spring.io/security/cve-2026-22732 and spring.io/security/cve-2026-59270, checked 13 November 2026.
CVEs since Spring Security 6.4 open-source support ended
Open-source support for 6.4 ended on 31 December 2025. Every fix since then ships only as a commercial 6.4 release, and spring.io lists no support of any kind for 6.4 after 31 December 2026. These are the 6.4 advisories in OSSeva's CVE directory.
Counts from the directory as of 20 October 2026 (Spring Security 6.4: 6 since 31 Dec 2025, 5 scored 7.0 or higher).
| Line | CVE | CVSS | Published | Issue | Fixed in (commercial builds only) |
|---|---|---|---|---|---|
| Spring Security 6.4 | CVE-2026-59270 | 9.1 | 27 Aug 2026 | Spring Security: embedded UnboundID LDAP server exposes a well-known admin bind DN on all interfaces | 6.4.19 |
| Spring Security 6.4 | CVE-2026-47841 | 7.4 | 26 Aug 2026 | Spring Security WebAuthn: user verification skipped with a distributed session store | 6.4.19 |
| Spring Security 6.4 | CVE-2026-47842 | 6.5 | 26 Aug 2026 | Spring Security: AesBytesEncryptor in CBC mode uses an all-zero IV | 6.4.19 |
| Spring Security 6.4 | CVE-2026-47838 | 8.1 | 10 Jun 2026 | Spring Security: SubjectDnX509PrincipalExtractor misreads malformed certificate CNs | 6.4.18 |
| Spring Security 6.4 | CVE-2026-40988 | 7.5 | 10 Jun 2026 | Spring Security SAML 2.0: REDIRECT binding inflates compressed payloads without a limit | 6.4.17 |
| Spring Security 6.4 | CVE-2026-22732 | 9.1 | 19 Mar 2026 | Spring Security: HTTP security headers may not be written in servlet applications | 6.4.15 |
The directory lists Spring Security CVEs matched at NVD to the product, mostly with a CVSS score of 7.0 or higher, so it is a subset of every Spring Security advisory. Fixed-in versions are from the Spring advisories; releases after the open-source end date are commercial builds.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to Spring Security 7.1 | Usually by moving Spring Boot from 3.4 to 4.1, by way of the latest 3.5.x. | Weeks to months | Engineering time | The supported path, open source to 31 July 2027. |
| Broadcom commercial support | Commercial 6.4 releases until 31 December 2026; 6.5 to 30 June 2032. | Procurement | Commercial subscription | Covers 6.4 for seven more weeks. A move to 6.5 extends the runway to 2032. |
| OSSeva patched Spring Security 6.4 | Signed 6.x artifacts with backported fixes for the core, web, OAuth2, SAML and WebAuthn modules. | Days | Subscription | For applications that need time for the Boot 4 move, and for after 31 December 2026. |
| Stay on 6.4.13 | No open source fixes since December 2025. | None | Zero now | Two critical advisories already apply. The authentication layer is the worst place to carry them. |
What OSSeva does for Spring Security 6.4
OSSeva patches this line
OSSeva ships patched, signed Spring Security 6.x artifacts, from 6.0 to 6.5, with backported fixes for the core, web, OAuth2, SAML and WebAuthn modules, delivered through your own repository manager. They are available on the Patch, Assure and Operate tiers, and cover 6.4 after 31 December 2026.
Spring Security extended supportWhat your auditor will say
Every system component in the cardholder data environment needs its applicable security patches. The authentication layer of an application is in scope, and a component with no supplier fix needs a patched source or a documented compensating control.
Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.
When does Spring Security 6.4 reach end of life?
Open source support ended on 31 December 2025. spring.io lists commercial support until 31 December 2026, and after that Broadcom ships no fixes for 6.4.
What is the last open source Spring Security 6.4 release?
6.4.13, published to Maven Central on 17 November 2025. It is the version Spring Boot 3.4.13 manages.
Is Spring Security 6.4 still supported?
Only commercially, and only until 31 December 2026. No open source 6.4 release has shipped since 6.4.13.
Which Spring Boot version uses Spring Security 6.4?
Spring Boot 3.4. Boot 3.5 uses 6.5, Boot 4.0 uses 7.0 and Boot 4.1 uses 7.1.
What should I upgrade Spring Security 6.4 to?
Spring Security 7.1, usually by moving Spring Boot to 4.1 by way of the latest 3.5.x. 6.5 is out of open source support too, so it is only a stepping stone.
Can I get security patches for Spring Security 6.4?
Yes. Broadcom sells commercial 6.4 releases to 31 December 2026, and OSSeva ships patched, signed Spring Security 6.x artifacts on the Patch, Assure and Operate tiers.
Get a quote
Still running Spring Security 6.4?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.
Prefer to talk or read more first?