Spring Security End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 7.1.3

Spring Security end of life (EOL) and end of support (EOS) dates: 16 Spring Security versions have reached EOL, including Spring Security 6.5 (EOL date: Jun 30, 2026) — no longer receiving security updates or patches. Spring Security 7.0 reaches its End of Support date on Dec 31, 2026 — plan your upgrade path now. Spring Security 7.1.3 is the current supported release, with support through Jul 31, 2027. Also see Graylog EOSL dates for related end-of-life information.

Spring Security end of life dates timeline — release schedule chart of the 8 most recent Spring Security versions, mapping security support and extended support windows against their EOL dates
Spring Security end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent Spring Security releases of 18 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Spring Security EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Spring Security Releases - Active EOS/EOSL Support (1)

Release Released OSS support Commercial Support Latest
7.1 (5 months ago) (in 8 months) (in 1 year and 8 months) 7.1.3 (2 days ago)

Spring Security Releases Nearing End of Life - Support Ending Soon (1)

Important: The following Spring Security releases will reach End of Life (EOL) within 6 months. Plan your migration to a supported release to ensure continued security updates and support.
Release Released OSS support Commercial Support Latest
7.0 (1 year ago) (in 1 month and 1 week) (in 1 year and 1 month) 7.0.9 (2 days ago)

Spring Security End of Life (EOL) Releases - No Longer Supported (16)

Release Released OSS support Commercial Support Latest
6.5 (1 year and 6 months ago) (4 months ago) (in 5 years and 7 months) 6.5.11 (5 months ago)
6.4 (2 years ago) (10 months ago) (in 1 month and 1 week) 6.4.13 (1 year ago)
6.3 (2 years and 6 months ago) (1 year and 4 months ago) (4 months ago) 6.3.10 (1 year and 5 months ago)
6.2 (3 years ago) (1 year and 10 months ago) (10 months ago) 6.2.8 (2 years ago)
6.1 (3 years and 6 months ago) (2 years and 4 months ago) (1 year and 4 months ago) 6.1.9 (2 years and 7 months ago)
5.8 (4 years ago) (2 years and 10 months ago) (in 2 years and 7 months) 5.8.16 (2 years ago)
6.0 (4 years ago) (2 years and 10 months ago) (1 year and 10 months ago) 6.0.8 (3 years and 1 month ago)
5.7 (4 years and 6 months ago) (3 years and 4 months ago) (in 2 years and 7 months) 5.7.14 (2 years ago)
5.6 (5 years ago) (3 years and 11 months ago) (2 years and 8 months ago) 5.6.12 (3 years and 4 months ago)
5.5 (5 years and 6 months ago) (4 years and 5 months ago) (3 years and 2 months ago) 5.5.8 (4 years and 6 months ago)
5.4 (6 years and 2 months ago) (4 years and 11 months ago) (3 years and 8 months ago) 5.4.10 (4 years and 11 months ago)
5.3 (6 years and 8 months ago) (5 years and 5 months ago) (4 years and 2 months ago) 5.3.13 (4 years and 11 months ago)
5.2 (7 years and 1 month ago) (6 years ago) (4 years and 9 months ago) 5.2.15 (4 years and 11 months ago)
5.1 (8 years ago) (7 years ago) (5 years and 9 months ago) 5.1.13 (6 years and 1 month ago)
5.0 (8 years and 7 months ago) (7 years and 7 months ago) (6 years and 4 months ago) 5.0.19 (6 years and 1 month ago)
4.2 (9 years and 9 months ago) (7 years and 2 months ago) (5 years and 11 months ago) 4.2.20 (5 years and 11 months ago)

If you run authentication and authorization through the project, Spring Security end of life dates decide how long you keep getting free fixes. Each line has a support window, and when it closes you must upgrade, buy extended support or accept the exposure. As of late October 2026 the latest release is 7.1, and 7.0 loses open-source updates on 31 December 2026.

Spring Security End of Life Dates for Every Supported Release

The table lists the released versions you are most likely to meet, with each release date and when free and paid updates stop.

VersionReleasedFree updates endPaid updates end
7.19 Jun 202631 Jul 202731 Jul 2028
7.017 Nov 202531 Dec 202631 Dec 2027
6.519 May 202530 Jun 202630 Jun 2032
6.418 Nov 202431 Dec 202531 Dec 2026
6.320 May 202430 Jun 202530 Jun 2026
5.821 Nov 202231 Dec 202330 Jun 2029

Any line whose free date has passed is end-of-life for open-source users. Versions 6.5 and 6.4 are past that point today, while 6.3 has lost paid updates too. Only 7.1 and 7.0 are fully supported.

Spring Security Support Policy and Release Schedule

The Spring Security support policy follows the VMware Tanzu rules: a major version is supported for at least three years, a minor version for at least 12 months, and you must run a supported minor. Every release is published on Maven Central, with no private repository reserved for paying customers. The release schedule and milestones pages show what is coming, and the support roadmap explains the details.

OSS Support vs Commercial Support

Between the end of OSS support and EOL, expect releases only for critical bugs and security issues. After that, VMware sells longer coverage for lines like 6.5, which stays covered until 2032.

Spring Framework and Spring Boot Timelines Behind Spring Security Versions

A release is marked EOL when the Spring Framework minor it aligns with is, or otherwise when its matching Spring Boot minor is. That means your Java applications answer to three lifecycle timelines, not one. Because Spring Framework is a transitive dependency of nearly every Spring project, teams often run an expired line without noticing.

How Spring Framework Alignment Sets EOL Dates

Spring Framework 6.2 lost free updates on 30 June 2026, and Spring Boot 3.5 ships on that Spring Framework line, so a Boot 3.5 build inherits the exposure. Spring Framework 7.0 is the current feature branch. Check the Spring Framework pin in your Maven build, and the Maven coordinates it resolves, before trusting a Spring Boot number.

Security Updates Stop at EOL: CVEs and Compliance Risk

Once a Spring Security line is EOL, no free patch reaches Maven Central. A new CVE against it stays open, which creates compliance risk for any enterprise audit. The pattern is visible in Spring Framework: CVE-2025-41242, a path traversal, was disclosed after 6.1 expired and was fixed only in 6.2.10, and any Spring Security line aligned to that Framework minor inherits the same exposure. Unpatched vulnerabilities like this are the real cost of waiting. One patch on a dead line is rare; assume zero further patches.

Extended Support and Upgrade Options for End-of-Life Spring Security

  • Move to a newer line: go to 7.1 or 7.0. The migration usually needs Java 17 as a minimum JDK, and Spring Framework 7.0 targets Java 17 to 25 with Jakarta EE 11 or 12.
  • Pay for longer cover: HeroDevs Never-Ending Support and other vendors cover lines after free updates stop.
  • Stay on LTS where one exists: Spring Framework 5.3 is flagged LTS, though its free window ended in 2024.

Track new dates on the GitHub wiki or endoflife.date, and recheck them whenever you bump a Spring Boot version, since any new patches follow the supported lines only.

EOL dates of related software products