CompatHub
Check EOL

Apache Cassandra 2.0 lifecycle

Current status

end of lifehigh

Apache Cassandra 2.0 reached end of life on 6 Nov 2015. 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
6 Nov 2015
Latest release
2.0.17
Released
18 Sept 2015

At a glance

Version line
2.0
Initial release
28 Aug 2013
Lifecycle phase
end of life
Latest stable
2.0.17
Latest release date
18 Sept 2015
EOL
6 Nov 2015
Risk
high
Releases tracked
18

Lifecycle timeline

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

  1. Release

    28 Aug 2013

  2. standard support

    28 Aug 2013 → 6 Nov 2015

    Source: Apache Cassandra Downloads

  3. end of lifecurrent

    6 Nov 2015 → —

    Source: Apache Cassandra Downloads

Apache Cassandra 2.0 reached end of life on 6 Nov 2015. 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 2.0

End of lifeEOL 6 November 2015

Supported upgrade options

Open full upgrade planner for Apache Cassandra 2.0 →

Security

Advisories affecting Apache Cassandra 2.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

2.0.17

Released 18 Sept 2015 · stable

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

Previous releases

  • 2.0.16

    18 Jun 2015

  • 2.0.15

    13 May 2015

  • 2.0.14

    30 Mar 2015

Release history

18 concrete releases tracked for this line.

VersionRelease dateChannelSource
2.0.1718 Sept 2015stableSource
2.0.1618 Jun 2015stableSource
2.0.1513 May 2015stableSource
2.0.1430 Mar 2015stableSource
2.0.1313 Mar 2015stableSource
2.0.1217 Jan 2015stableSource
2.0.1121 Oct 2014stableSource
2.0.1022 Aug 2014stableSource
2.0.926 Jun 2014stableSource
2.0.821 May 2014stableSource
2.0.714 Apr 2014stableSource
2.0.67 Mar 2014stableSource
2.0.55 Feb 2014stableSource
2.0.427 Dec 2013stableSource
2.0.322 Nov 2013stableSource
2.0.224 Oct 2013stableSource
2.0.120 Sept 2013stableSource
2.0.028 Aug 2013stableSource

Release activity

Total releases
18
Last 30 days
0
Last 90 days
0
Avg. interval
~44 days
Most recent
18 Sept 2015

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.

2.05.0
Statusend of lifestandard support
Latest release2.0.175.0.9
EOLNov 2015Not 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
18
Lifecycle periods
2
EOL
Known
Provenance records
3
Data last checked
2 Sept 2026
Latest source update
2 Sept 2026

Other Apache Cassandra versions