← ← Back to all products
All badges & lifecycle API →
Apache SparkEnd of Life (EOL) Dates & Support Status
Active
MiddlewareLatest Version: 4.0.4Latest Release: Jul 12, 2026
Apache Spark is a unified analytics engine for large-scale data processing with built-in modules for SQL, streaming, and ML.
Support summary
Apache Spark 4.0 reaches EOL in 57 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Nov 23, 2026
Apache Spark 4.0 · 57 days left
Supported cycles
4
2 lts
Versions
21
Latest Version
4.0.4
Active Support
4
EOL
17
Lifecycle Timeline
Oct 29, 2018As of Sep 27, 2026
4.2Active · Jan 11, 2028
4.1Active · Jun 11, 2027
4.0Active · Nov 23, 2026
3.5Active · Nov 30, 2027
3.4EOL · Oct 21, 2024
3.3EOL · Dec 9, 2023
3.2EOL · Apr 9, 2023
3.1EOL · Aug 22, 2022
3.0EOL · Dec 6, 2021
2.4EOL · May 9, 2021
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4.2 | Jul 14, 2026 | Maintained | Jan 11, 2028 | 4.2.0 | No | Active |
| 4.1 | Dec 11, 2025 | Maintained | Jun 11, 2027 | 4.1.3 | No | Active |
| 4.0 | May 19, 2025 | Maintained | Nov 23, 2026 | 4.0.4 | No | Active |
| 3.5 | Sep 9, 2023 | Maintained | Nov 30, 2027 | 3.5.9 | Yes | Active |
| 3.4 | Apr 7, 2023 | Ended | Oct 21, 2024 | 3.4.4 | No | EOL |
| 3.3 | Jun 9, 2022 | Ended | Dec 9, 2023 | 3.3.4 | No | EOL |
| 3.2 | Oct 6, 2021 | Ended | Apr 9, 2023 | 3.2.4 | No | EOL |
| 3.1 | Feb 22, 2021 | Ended | Aug 22, 2022 | 3.1.3 | No | EOL |
| 3.0 | Jun 6, 2020 | Ended | Dec 6, 2021 | 3.0.3 | No | EOL |
| 2.4 | Oct 29, 2018 | Ended | May 9, 2021 | 2.4.8 | Yes | EOL |
| 2.3 | Feb 22, 2018 | Ended | Aug 25, 2019 | 2.3.4 | No | EOL |
| 2.2 | Jun 30, 2017 | Ended | Jan 30, 2019 | 2.2.3 | No | EOL |
| 2.1 | Dec 15, 2016 | Ended | Jun 26, 2018 | 2.1.3 | No | EOL |
| 2.0 | Jul 19, 2016 | Ended | Dec 15, 2016 | 2.0.2 | No | EOL |
| 1.6 | Dec 21, 2015 | Ended | Jul 19, 2016 | 1.6.3 | No | EOL |
| 1.5 | Sep 8, 2015 | Ended | Dec 21, 2015 | 1.5.2 | No | EOL |
| 1.4 | Jun 2, 2015 | Ended | Sep 8, 2015 | 1.4.1 | No | EOL |
| 1.3 | Mar 5, 2015 | Ended | Jun 2, 2015 | 1.3.1 | No | EOL |
| 1.2 | Dec 10, 2014 | Ended | Apr 5, 2015 | 1.2.2 | No | EOL |
| 1.1 | Sep 3, 2014 | Ended | Dec 10, 2014 | 1.1.1 | No | EOL |
| 1.0 | May 26, 2014 | Ended | Sep 3, 2014 | 1.0.2 | No | EOL |
Data sources
Embed this badge
Show Apache Spark's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/apache-spark/)HTML
<a href="https://eol.wiki/apache-spark/"><img src="https://eol.wiki/badge/apache-spark.svg" alt="Apache Spark end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Apache Spark have reached end of life?
The following Apache Spark versions have reached end of life and no longer receive security updates: 3.4, 3.3, 3.2, 3.1, 3.0, 2.4, 2.3, 2.2 (and 9 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Apache Spark 3.4?
Apache Spark 3.4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache Spark?
The latest version of Apache Spark is 4.0.4, released in the 4.0 release cycle.
How many versions of Apache Spark are currently supported?
Apache Spark currently has 4 actively supported version(s): 4.2, 4.1, 4.0, 3.5.
When does Apache Spark 4.2 reach end of life?
Apache Spark 4.2 is scheduled to reach end of life on Jan 11, 2028.
What should I do when Apache Spark reaches end of life?
When a Apache Spark version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.