Spring Batch End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Spring Batch versions. Dates read at the vendor's own lifecycle pages (spring.io). Updated at every deploy.
Spring Batch 6.0 is supported until July 2027, its end-of-support date. It is also the next Spring Batch version to reach end of life. 8 of 9 tracked Spring Batch versions are past end of life; the most recent to reach it, 5.2, did so in June 2026. The full Spring Batch lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓GET https://api.endoflife.ai/v1/score/spring-batch/6.0 returns this version's end-of-life date, its source and the EOL Risk Score as JSON. Get a free API key (150 requests a day, no expiry).| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 3.0 | 3.0.10 | May 22, 2014 | Aug 2019 | Nov 2020 Tanzu Spring commercial support (ended) |
EOL since August 2019 | EOL |
| 4.0 | 4.0.4 | Dec 1, 2017 | Mar 2019 | Jun 2020 Tanzu Spring commercial support (ended) |
EOL since March 2019 | EOL |
| 4.1 | 4.1.4 | Oct 29, 2018 | Oct 2019 | Jan 2021 Tanzu Spring commercial support (ended) |
EOL since October 2019 | EOL |
| 4.2 | 4.2.8 | Oct 1, 2019 | May 2021 | Aug 2022 Tanzu Spring commercial support (ended) |
EOL since May 2021 | EOL |
| 4.3 | 4.3.10 | Oct 28, 2020 | Jun 2023 | Jun 2029 Tanzu Spring commercial support |
EOL since June 2023 | EOL |
| 5.0 | 5.0.6 | Nov 24, 2022 | Jun 2024 | Jun 2025 Tanzu Spring commercial support (ended) |
EOL since June 2024 | EOL |
| 5.1 | 5.1.3 | Nov 22, 2023 | Jun 2025 | Jun 2026 Tanzu Spring commercial support (ended) |
EOL since June 2025 | EOL |
| 5.2 | 5.2.6 | Nov 21, 2024 | Jun 2026 | Jun 2032 Tanzu Spring commercial support |
EOL since June 2026 | EOL |
| 6.0 | 6.0.6 | Nov 19, 2025 | Jul 2027 | Jul 2028 Tanzu Spring commercial support |
EOL in July 2027 | Active |
[](https://endoflife.ai/spring-batch)
Spring Batch lifecycle status — the real story
Spring Batch, the Spring project for batch processing on the JVM: chunk-oriented jobs, restartable steps and a job repository (spring-projects/spring-batch on GitHub, Maven coordinates org.springframework.batch:spring-batch-core); one line per minor version. Release days are the Maven Central publish dates from repo1.maven.org/maven2/org/springframework/batch/spring-batch-core, the directory listing and the jar upload stamp in each version directory agreeing on both ends of every line. Older Maven versions carry a .RELEASE suffix; the plain number is shown. A generation that Spring's table already names but that has only milestones or release candidates on Maven Central is not listed until its first general-availability release.
End-of-life rule: support dates are the vendor's own, from the Spring generations table (api.spring.io/projects/spring-batch/generations, and the same months in the data behind spring.io/projects/spring-batch#support). The mapping is the one used for Spring Boot: eol is the end of open-source support (ossSupportEndDate) and extendedSupport is the end of commercial, enterprise support from Broadcom (commercialSupportEndDate). Spring states these to the month only, so the page prints months and the stored value is the last day of that month. Spring's support policy ties each project's support dates to the Spring Boot generation that manages it. A Spring Batch line can serve more than one Spring Boot generation, so its open-source window can run longer than a single Spring Boot minor's, and the lines Spring marks as extended carry the long commercial window. Release lines older than the vendor table are not listed: Spring publishes no end date for them.
On several older lines the last open-source release on Maven Central is dated after the stated open-source end month; the vendor's stated month is what is served. The latest version shown for a line is the last open-source release on Maven Central; releases made afterwards under commercial support are not published there and are not listed.
Spring Batch release and support pattern
Across the 9 release lines with a published release date, Spring Batch has shipped a new line roughly every 1 year (median interval). A line typically stays in standard support for about 1.6 years from its release to its standard-support end date.
Of the 9 release lines tracked, 8 are past end of life and 1 is still within support. The newest line, 6.0, was released November 19, 2025. The next scheduled end of life is 6.0 in July 2027 (the vendor names the month only). Upstream also publishes an extended-support phase for 9 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Spring Batch end of life mean for your organization?
When a version of Spring Batch reaches end of life, the vendor's standard security patches for that version stop. Vulnerabilities found after that date are still published on the National Vulnerability Database, exploit code often becomes public, and systems on that version stay exposed until they are upgraded or covered by extended support.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but the vendor's policy provides no patch for the ended version. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Spring Batch 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.
Your options when Spring Batch reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Spring Batch version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Spring Batch has 8 versions past end of life — standard security patches have stopped; 2 of them are still covered by Tanzu Spring commercial support, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Spring Batch is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."