Apache Spark End of Life Dates
other
Developers working with large-scale data processing rely on a unified analytics engine to streamline their workflow, and Apache Spark has been a go-to solution since its inception. Created to provide an interface for programming clusters with implicit data parallelism and fault tolerance, Apache Spark has become an essential tool for many. The Apache Software Foundation maintains this open-source project, ensuring it remains a viable option for developers. With its ability to handle massive amounts of data, Spark has become a staple in the industry, and its widespread adoption is a testament to its effectiveness.
The end-of-life landscape for Apache Spark is characterized by a significant number of versions that are no longer supported, with 17 out of 20 versions having reached their end-of-life. Currently, only three versions remain active, with the latest stable version being 3.5.8. Looking ahead, the next version slated to reach its end-of-life is version 4.0, which is set to expire on November 23, 2026. This gives developers ample time to plan and prepare for the transition to a newer version. The most recent end-of-life date was October 21, 2024, for version 3.4, marking the end of support for that particular iteration.
From a security standpoint, Apache Spark has a spotless record, with no known CVEs tracked to date. This means that there are no critical vulnerabilities to speak of, and as a result, there is no most affected version. With no CVEs to contend with, developers can focus on utilizing Spark's capabilities without worrying about potential security risks. Given its clean security record and the fact that only a few versions are still supported, developers should take this opportunity to review their current Spark setup and plan for any necessary upgrades to ensure continued support and optimal performance.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 4.2 | Jul 14, 2026 | — | Jan 11, 2028 | in 536d | 4.2.0 | — | Active | |
| 4.1 | Dec 11, 2025 | — | Jun 11, 2027 | in 322d | 4.1.3 | — | Active | |
| 4.0 | May 19, 2025 | — | Nov 23, 2026 | in 122d | 4.0.4 | — | Active | |
| 3.5 LTS | Sep 9, 2023 | — | Nov 30, 2027 | in 494d | 3.5.9 | — | Active | |
| 3.4 | Apr 7, 2023 | — | Oct 21, 2024 | 641d ago | 3.4.4 | — | EOL | |
| 3.3 | Jun 9, 2022 | — | Dec 9, 2023 | 958d ago | 3.3.4 | — | EOL | |
| 3.2 | Oct 6, 2021 | — | Apr 9, 2023 | 1202d ago | 3.2.4 | — | EOL | |
| 3.1 | Feb 22, 2021 | — | Aug 22, 2022 | 1432d ago | 3.1.3 | — | EOL | |
| 3.0 | Jun 6, 2020 | — | Dec 6, 2021 | 1691d ago | 3.0.3 | — | EOL | |
| 2.4 LTS | Oct 29, 2018 | — | May 9, 2021 | 1902d ago | 2.4.8 | — | EOL | |
| 2.3 | Feb 22, 2018 | — | Aug 25, 2019 | 2525d ago | 2.3.4 | — | EOL | |
| 2.2 | Jun 30, 2017 | — | Jan 30, 2019 | 2732d ago | 2.2.3 | — | EOL | |
| 2.1 | Dec 15, 2016 | — | Jun 26, 2018 | 2950d ago | 2.1.3 | — | EOL | |
| 2.0 | Jul 19, 2016 | — | Dec 15, 2016 | 3508d ago | 2.0.2 | — | EOL | |
| 1.6 | Dec 21, 2015 | — | Jul 19, 2016 | 3657d ago | 1.6.3 | — | EOL | |
| 1.5 | Sep 8, 2015 | — | Dec 21, 2015 | 3868d ago | 1.5.2 | — | EOL | |
| 1.4 | Jun 2, 2015 | — | Sep 8, 2015 | 3972d ago | 1.4.1 | — | EOL | |
| 1.3 | Mar 5, 2015 | — | Jun 2, 2015 | 4070d ago | 1.3.1 | — | EOL | |
| 1.2 | Dec 10, 2014 | — | Apr 5, 2015 | 4128d ago | 1.2.2 | — | EOL | |
| 1.1 | Sep 3, 2014 | — | Dec 10, 2014 | 4244d ago | 1.1.1 | — | EOL | |
| 1.0 | May 26, 2014 | — | Sep 3, 2014 | 4342d ago | 1.0.2 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
