Apache Spark 3.5 · Version Status

Apache Spark 3.5 End of Life Date

Apache Spark 3.5 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Apache Spark 3.5 is actively supported. EOL date: November 30, 2027.
EOL Date
Nov 30, 2027
570 days remaining
Latest Release
3.5.8
LTS release
Release Date
Sep 9, 2023
Apache Spark 3.5 series
← Apache Spark 3.4 All Apache Spark versions Apache Spark 4.0 →
All Apache Spark Versions
VersionLatestEOL DateStatus
1.0 1.0.2 Sep 3, 2014 EOL
1.1 1.1.1 Dec 10, 2014 EOL
1.2 1.2.2 Apr 5, 2015 EOL
1.3 1.3.1 Jun 2, 2015 EOL
1.4 1.4.1 Sep 8, 2015 EOL
1.5 1.5.2 Dec 21, 2015 EOL
1.6 1.6.3 Jul 19, 2016 EOL
2.0 2.0.2 Dec 15, 2016 EOL

What does Apache Spark 3.5 end of life mean?

When Apache Spark 3.5 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Apache Spark 3.5 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Apache Spark 4.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Apache Spark 3.5 reach end of life?
Apache Spark 3.5 reached end of life on November 30, 2027. That is 570 days remaining.
Is Apache Spark 3.5 still supported?
Yes, Apache Spark 3.5 is currently supported. The EOL date is November 30, 2027.
What should I upgrade to from Apache Spark 3.5?
The recommended upgrade from Apache Spark 3.5 is Apache Spark 4.1 — the latest actively supported version. Check the Apache Spark full timeline for all supported versions.
What are the security risks of running Apache Spark 3.5 past EOL?
When Apache Spark 3.5 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Apache Spark should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →