Apache Spark End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Apache Spark versions. Data from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
Apache Spark 4.3 is supported until April 30, 2028, its end-of-support date. The next Apache Spark version to reach end of life is 4.0, on November 23, 2026. 17 of 22 tracked Apache Spark versions are past end of life; the most recent to reach it, 3.4, did so on October 21, 2024. The full Apache Spark 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 ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.2 | May 26, 2014 | Sep 3, 2014 | 4449 days past EOL | EOL |
| 1.1 | 1.1.1 | Sep 3, 2014 | Dec 10, 2014 | 4351 days past EOL | EOL |
| 1.2 | 1.2.2 | Dec 10, 2014 | Apr 5, 2015 | 4235 days past EOL | EOL |
| 1.3 | 1.3.1 | Mar 5, 2015 | Jun 2, 2015 | 4177 days past EOL | EOL |
| 1.4 | 1.4.1 | Jun 2, 2015 | Sep 8, 2015 | 4079 days past EOL | EOL |
| 1.5 | 1.5.2 | Sep 8, 2015 | Dec 21, 2015 | 3975 days past EOL | EOL |
| 1.6 | 1.6.3 | Dec 21, 2015 | Jul 19, 2016 | 3764 days past EOL | EOL |
| 2.0 | 2.0.2 | Jul 19, 2016 | Dec 15, 2016 | 3615 days past EOL | EOL |
| 2.1 | 2.1.3 | Dec 15, 2016 | Jun 26, 2018 | 3057 days past EOL | EOL |
| 2.2 | 2.2.3 | Jun 30, 2017 | Jan 30, 2019 | 2839 days past EOL | EOL |
| 2.3 | 2.3.4 | Feb 22, 2018 | Aug 25, 2019 | 2632 days past EOL | EOL |
| 2.4 LTS | 2.4.8 | Oct 29, 2018 | May 9, 2021 | 2009 days past EOL | EOL |
| 3.0 | 3.0.3 | Jun 6, 2020 | Dec 6, 2021 | 1798 days past EOL | EOL |
| 3.1 | 3.1.3 | Feb 22, 2021 | Aug 22, 2022 | 1539 days past EOL | EOL |
| 3.2 | 3.2.4 | Oct 6, 2021 | Apr 9, 2023 | 1309 days past EOL | EOL |
| 3.3 | 3.3.4 | Jun 9, 2022 | Dec 9, 2023 | 1065 days past EOL | EOL |
| 3.4 | 3.4.4 | Apr 7, 2023 | Oct 21, 2024 | 748 days past EOL | EOL |
| 3.5 LTS | 3.5.9 | Sep 9, 2023 | Nov 2027 | EOL in November 2027 | Active |
| 4.0 | 4.0.5 | May 19, 2025 | Nov 23, 2026 | 15 days remaining | Warning |
| 4.1 | 4.1.4 | Dec 11, 2025 | Jun 11, 2027 | 215 days remaining | Active |
| 4.2 | 4.2.1 | Jul 14, 2026 | Jan 11, 2028 | 429 days remaining | Active |
| 4.3 | 4.3.0 | Oct 30, 2026 | Apr 30, 2028 | 539 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/apache-spark)
Apache Spark release and support pattern
Across the 22 release lines with a published release date, Apache Spark has shipped a new line roughly every 7 months (median interval). A line typically stays supported for about 1.5 years from its release to its end-of-life date. 2 of the 22 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 22 release lines tracked, 17 are past end of life and 5 are still within support. The newest line, 4.3, was released October 30, 2026. The next scheduled end of life is 4.0 on November 23, 2026 — 14 days from this build. The longest-supported line currently published is 4.3, to April 30, 2028.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Apache Spark security intelligence
CISA KEV history: Apache Spark is named in CISA's Known Exploited Vulnerabilities catalog 1 time, most recently on 2023-03-07. Derived from CISA's live catalog at every build.
What does Apache Spark end of life mean for your organization?
When a version of Apache Spark 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: 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 no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Apache Spark 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 Apache Spark 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 Apache Spark version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Apache Spark has 17 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Apache Spark 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."