Apache Cassandra 3.11 · Version Status
Apache Cassandra 3.11 End of Life Date
Apache Cassandra 3.11 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Apache Cassandra 3.11 is past end of life. This version no longer receives security patches. 737 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 5, 2024
737 days past EOL
Latest Release
3.11.19
Standard release
Release Date
Jun 23, 2017
Apache Cassandra 3.11 series
Lifecycle detail
Apache Cassandra 3.11 was released on June 23, 2017 and support ended on September 5, 2024 — a supported lifespan of 7 years and 3 months. The last patch it will ever receive is 3.11.19, published February 7, 2025 — 5 months after the published end-of-life date. It has been without security patches for 2 years.
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 → ·
View score card →
Extended Support
Extended Apache Cassandra 3.11 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Apache Cassandra Versions
| Version | Latest | EOL Date | Status |
|---|
| 3.0 |
3.0.32 |
Sep 5, 2024 |
EOL |
| → 3.11 |
3.11.19 |
Sep 5, 2024 |
EOL |
| 4.0 |
4.0.21 |
EOL |
Active |
| 4.1 |
4.1.12 |
EOL |
Active |
| 5.0 |
5.0.9 |
EOL |
Active |
What does Apache Cassandra 3.11 end of life mean?
When Apache Cassandra 3.11 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 Cassandra 3.11 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Apache Cassandra 5.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Apache Cassandra 3.11 reach end of life?
Apache Cassandra 3.11 reached end of life on September 5, 2024. This version is no longer receiving security patches.
Is Apache Cassandra 3.11 still supported?
No. Apache Cassandra 3.11 reached end of life on September 5, 2024 and is no longer receiving security patches.
What should I upgrade to from Apache Cassandra 3.11?
The recommended upgrade from Apache Cassandra 3.11 is
Apache Cassandra 5.0 — the latest actively supported version. Check the
Apache Cassandra full timeline for all supported versions.
What are the security risks of running Apache Cassandra 3.11 past EOL?
When Apache Cassandra 3.11 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 Cassandra should migrate immediately or implement compensating controls.