CompatHub
Check EOL

Apache Cassandra 3.0 lifecycle

Current status

end of lifehigh

Apache Cassandra 3.0 reached end of life on 19 Jun 2017. Security and bug fixes are no longer provided by the project according to published lifecycle data.

This line is end of life.

Plan your upgrade →

Security: 2 tracked advisories affecting this line. Details below — lifecycle and vulnerability status are separate.

Official lifecycle source: Apache Cassandra Downloads

Support phase
end of life
End of life
19 Jun 2017
Latest release
3.0.32
Released
6 Feb 2025

At a glance

Version line
3.0
Initial release
6 Nov 2015
Lifecycle phase
end of life
Latest stable
3.0.32
Latest release date
6 Feb 2025
EOL
19 Jun 2017
Risk
high
Releases tracked
33

Lifecycle timeline

Phases from published LifecyclePeriod records. Missing phases are not inferred.

  1. Release

    6 Nov 2015

  2. standard support

    6 Nov 2015 → 19 Jun 2017

    Source: Apache Cassandra Downloads

  3. end of lifecurrent

    19 Jun 2017 → —

    Source: Apache Cassandra Downloads

Apache Cassandra 3.0 reached end of life on 19 Jun 2017. Security and bug fixes are no longer provided by the project according to published lifecycle data.

Upgrade options

Newer supported Apache Cassandra version lines from CompatHub lifecycle data. Compatibility and security context use existing evidence only.

You are on Apache Cassandra 3.0

End of lifeEOL 19 June 2017

Supported upgrade options

Open full upgrade planner for Apache Cassandra 3.0 →

Security

Advisories affecting Apache Cassandra 3.0 (OSV.dev evidence). Known exploited status, due dates, and ransomware use from CISA KEV when matched.

Known vulnerabilities
2
Known exploited
0
Highest CVSS
—
  • CVE-2025-23015GHSA-wmcc-9vch-jmx4

    Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions

    Affected:
    <3.0.31
    Fixed in:
    3.0.31
    Source:
    OSV source · Advisory
  • CVE-2021-44521GHSA-8ffc-79xg-29w8

    Apache Cassandra vulnerable to Code Injection due to unsafe configuration

    Affected:
    <3.0.26
    Fixed in:
    3.0.26
    Source:
    OSV source · Advisory

Latest release

3.0.32

Released 6 Feb 2025 · stable

https://github.com/apache/cassandra/releases/tag/cassandra-3.0.32

Previous releases

  • 3.0.31

    27 Jan 2025

  • 3.0.30

    11 Apr 2024

  • 3.0.29

    5 May 2023

Release history

33 concrete releases tracked for this line.

VersionRelease dateChannelSource
3.0.326 Feb 2025stableSource
3.0.3127 Jan 2025stableSource
3.0.3011 Apr 2024stableSource
3.0.295 May 2023stableSource
3.0.2819 Oct 2022stableSource
3.0.276 May 2022stableSource
3.0.267 Feb 2022stableSource
3.0.2525 Jul 2021stableSource
3.0.2429 Jan 2021stableSource
3.0.2329 Oct 2020stableSource
3.0.2228 Aug 2020stableSource
3.0.2114 Jul 2020stableSource
3.0.2010 Feb 2020stableSource
3.0.1924 Oct 2019stableSource
3.0.181 Feb 2019stableSource
3.0.1716 Jul 2018stableSource
3.0.1613 Feb 2018stableSource
3.0.152 Oct 2017stableSource
3.0.1419 Jun 2017stableSource
3.0.1311 Apr 2017stableSource
3.0.127 Mar 2017stableSource
3.0.1116 Feb 2017stableSource
3.0.1011 Nov 2016stableSource
3.0.912 Sept 2016stableSource
3.0.81 Jul 2016stableSource

Release activity

Total releases
33
Last 30 days
0
Last 90 days
0
Avg. interval
~106 days
Most recent
6 Feb 2025

Should I use this version?

Not recommended for new deployments

Upgrade to a currently supported release line. Recommended target: Apache Cassandra 5.0.

Version comparison

Compact comparison against the nearest relevant release lines.

3.05.0
Statusend of lifestandard support
Latest release3.0.325.0.9
EOLJun 2017Not published
Riskhighlow

Sources

Where this information comes from.

Lifecycle sources

Release sources

Data coverage

Last checked = last successful upstream check. Latest source update = when upstream content last changed.

Releases tracked
33
Lifecycle periods
2
EOL
Known
Provenance records
3
Data last checked
2 Sept 2026
Latest source update
2 Sept 2026

Other Apache Cassandra versions