Spring Integration · Lifecycle Status

Spring Integration End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Spring Integration versions. Dates read at the vendor's own lifecycle pages (spring.io). Updated at every deploy.

⚡ Spring Integration 7.0 reaches end of life in December 2026. Plan your migration now — EOL in December 2026.

Spring Integration 7.1 is supported until July 2027, its end-of-support date. The next Spring Integration version to reach end of life is 7.0, in December 2026. 13 of 15 tracked Spring Integration versions are past end of life; the most recent to reach it, 6.5, did so in June 2026. The full Spring Integration 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 reminded before Spring Integration 7.0 reaches EOL in December 2026 — alerts 90, 30 & 7 days out.
Google → Subscribe to all dates
Subscribe keeps every Spring Integration end date in your calendar and updates itself. Calendar URL: https://endoflife.ai/calendar/spring-integration.ics
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
Automating this check? GET https://api.endoflife.ai/v1/score/spring-integration/7.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).
Latest Active
7.1.2
7.1 series
Next EOL
7.0
Dec 2026
Active Versions
1
of 15 total
EOL Versions
13
no longer patched
40 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
30/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
CPE Identifier
cpe:2.3:a:vmware:spring_integration
The Common Platform Enumeration name vulnerability scanners and CVE records use for Spring Integration. Verified against the NIST CPE dictionary. Machine-readable for all products: cpe-map.json
Package URLs (purl)
pkg:maven/org.springframework.integration/spring-integration-core
pkg:github/spring-projects/spring-integration
The package URL identifiers SBOM tools emit for Spring Integration, so a CycloneDX or SPDX component resolves to this page by exact identifier rather than by name. Machine-readable for all products: purl-map.json; whole-SBOM checks: POST /v1/sbom or the Stack Scanner.
Release Cycle Timeline
■ EOL   ■ Warning   ■ Active   ┊ Today
Release cycle timeline 201720182019202020212022202320242025202620274.35.05.15.25.35.45.56.06.16.26.36.46.57.07.1TODAY
13 versions of Spring Integration are past end of life — standard security patches have stopped; 3 of them are still covered by Tanzu Spring commercial support. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateExtended SupportDaysStatus
4.3 4.3.24 Jun 13, 2016 Aug 2019 Nov 2020
Tanzu Spring commercial support (ended)
EOL since August 2019 EOL
5.0 5.0.14 Nov 28, 2017 Mar 2019 Jun 2020
Tanzu Spring commercial support (ended)
EOL since March 2019 EOL
5.1 5.1.13 Oct 29, 2018 Oct 2019 Jan 2021
Tanzu Spring commercial support (ended)
EOL since October 2019 EOL
5.2 5.2.11 Oct 1, 2019 Oct 2020 Jan 2022
Tanzu Spring commercial support (ended)
EOL since October 2020 EOL
5.3 5.3.10 May 13, 2020 May 2021 Aug 2022
Tanzu Spring commercial support (ended)
EOL since May 2021 EOL
5.4 5.4.13 Oct 29, 2020 Nov 2021 Feb 2023
Tanzu Spring commercial support (ended)
EOL since November 2021 EOL
5.5 5.5.20 May 18, 2021 Jun 2023 Jun 2029
Tanzu Spring commercial support
EOL since June 2023 EOL
6.0 6.0.9 Nov 22, 2022 Dec 2023 Dec 2024
Tanzu Spring commercial support (ended)
EOL since December 2023 EOL
6.1 6.1.9 May 16, 2023 Jun 2024 Jun 2025
Tanzu Spring commercial support (ended)
EOL since June 2024 EOL
6.2 6.2.11 Nov 21, 2023 Dec 2024 Dec 2025
Tanzu Spring commercial support (ended)
EOL since December 2024 EOL
6.3 6.3.11 May 21, 2024 Jun 2025 Jun 2026
Tanzu Spring commercial support (ended)
EOL since June 2025 EOL
6.4 6.4.10 Nov 19, 2024 Dec 2025 Dec 2026
Tanzu Spring commercial support
EOL since December 2025 EOL
6.5 6.5.10 May 20, 2025 Jun 2026 Jun 2032
Tanzu Spring commercial support
EOL since June 2026 EOL
7.0 7.0.7 Nov 18, 2025 Dec 2026 Dec 2027
Tanzu Spring commercial support
EOL in December 2026 Warning
7.1 7.1.2 Jun 10, 2026 Jul 2027 Jul 2028
Tanzu Spring commercial support
EOL in July 2027 Active
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
EOL date vs extended support. The EOL Date column is the end of standard, included support. Tanzu Spring commercial support is a paid programme. Versions past their EOL date are only receiving patches if you hold that subscription — without it, they are unpatched. 3 versions of Spring Integration are past the standard EOL date but still inside the extended support window.
Spring Integration EOL status badge Live EOL badge for your README — updates automatically at every build. [![Spring Integration EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fspring-integration.json)](https://endoflife.ai/spring-integration)

Spring Integration lifecycle status — the real story

Spring Integration, the Spring project that implements the Enterprise Integration Patterns: message channels, endpoints and adapters for messaging inside an application and with external systems (spring-projects/spring-integration on GitHub, Maven coordinates org.springframework.integration:spring-integration-core); one line per minor version. Release days are the Maven Central publish dates from repo1.maven.org/maven2/org/springframework/integration/spring-integration-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-integration/generations, and the same months in the data behind spring.io/projects/spring-integration#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, 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 Integration release and support pattern

Across the 15 release lines with a published release date, Spring Integration has shipped a new line roughly every 6 months (median interval). A line typically stays in standard support for about 1.1 years from its release to its standard-support end date.

Of the 15 release lines tracked, 13 are past end of life and 2 are still within support. The newest line, 7.1, was released June 10, 2026. The next scheduled end of life is 7.0 in December 2026 (the vendor names the month only). The longest-supported line currently published is 7.1, to July 2027. Upstream also publishes an extended-support phase for 15 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 Integration end of life mean for your organization?

When a version of Spring Integration 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 Integration 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 Integration 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.

OptionBest whenWatch 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 Integration version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get Spring Integration Support Options

Spring Integration has 13 versions past end of life — standard security patches have stopped; 3 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 Integration 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."

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for Spring Integration?
The next Spring Integration version reaching EOL is 7.0 in December 2026. See the full table above for all version EOL dates.
When is the Spring Integration support end date?
The next Spring Integration support end date is December 2026, when version 7.0 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Spring Integration?
The latest active version of Spring Integration is 7.1.2. Always verify against the table above as support windows can change.
What happens when Spring Integration reaches end of life?
When Spring Integration reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor patch path — a growing attack surface that a CVE-based scan does not show. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give the date in advance.
How do I check if I'm running an EOL version of Spring Integration?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Spring Integration versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

✓ 45 of 45 lifecycle dates vendor-sourced · read from Spring (Broadcom) on 2026-11-18 · confidence: 30 high, 15 medium, 0 low (each version page shows where every date comes from) · provenance · Source: the vendor's own lifecycle pages (spring.io) · Generated at build time · How we source data →
Spring Integration end-of-life status badge