Spring Security End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Spring Security versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 4.2 | 4.2.20 | Jan 31, 2017 | Aug 31, 2019 | 2488 days past EOL | EOL |
| 5.0 | 5.0.19 | Mar 31, 2018 | Mar 31, 2019 | 2641 days past EOL | EOL |
| 5.1 | 5.1.13 | Oct 31, 2018 | Oct 31, 2019 | 2427 days past EOL | EOL |
| 5.2 | 5.2.15 | Oct 1, 2019 | Oct 31, 2020 | 2061 days past EOL | EOL |
| 5.3 | 5.3.13 | Mar 4, 2020 | May 31, 2021 | 1849 days past EOL | EOL |
| 5.4 | 5.4.10 | Sep 9, 2020 | Nov 30, 2021 | 1666 days past EOL | EOL |
| 5.5 | 5.5.8 | May 18, 2021 | May 31, 2022 | 1484 days past EOL | EOL |
| 5.6 | 5.6.12 | Nov 16, 2021 | Nov 30, 2022 | 1301 days past EOL | EOL |
| 5.7 | 5.7.14 | May 16, 2022 | Jun 30, 2023 | 1089 days past EOL | EOL |
| 5.8 | 5.8.16 | Nov 21, 2022 | Dec 31, 2023 | 905 days past EOL | EOL |
| 6.0 | 6.0.8 | Nov 21, 2022 | Dec 31, 2023 | 905 days past EOL | EOL |
| 6.1 | 6.1.9 | May 15, 2023 | Jun 30, 2024 | 723 days past EOL | EOL |
| 6.2 | 6.2.8 | Nov 20, 2023 | Dec 31, 2024 | 539 days past EOL | EOL |
| 6.3 | 6.3.10 | May 20, 2024 | Jun 30, 2025 | 358 days past EOL | EOL |
| 6.4 | 6.4.13 | Nov 18, 2024 | Dec 31, 2025 | 174 days past EOL | EOL |
| 6.5 | 6.5.11 | May 19, 2025 | Jun 30, 2026 | 7 days remaining | Warning |
| 7.0 | 7.0.6 | Nov 17, 2025 | Dec 31, 2026 | 191 days remaining | Active |
| 7.1 | 7.1.0 | Jun 9, 2026 | Jul 31, 2027 | 403 days remaining | Active |
What does Spring Security end of life mean for your organization?
When a version of Spring Security reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Spring Security should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Spring Security versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →