cassandra
Bitnami package
Overview
Package versions
| Versions | Range | Direct vulnerabilities |
|---|---|---|
| 5.0.8-0 | and later versions | 0C0H0M0L |
| 5.0.3 | up to 5.0.8-0 | 1C0H0M0L |
| 5.0.0 | up to 5.0.3 | 1C1H2M0L |
| 4.1.11-0 | up to 5.0.0 | 0C0H0M0L |
| 4.1.8 | up to 4.1.11-0 | 1C0H0M0L |
| 4.1.2 | up to 4.1.8 | 1C1H2M0L |
| 4.1.0 | up to 4.1.2 | 1C2H2M0L |
| 4.0.20 | up to 4.1.0 | 0C0H0M0L |
| 4.0.20-0 | up to 4.0.20 | 0C0H1M0L |
| 4.0.17 | up to 4.0.20-0 | 1C0H1M0L |
| 4.0.16 | up to 4.0.17 | 1C1H1M0L |
| 4.0.15 | up to 4.0.16 | 1C1H2M0L |
| 4.0.10 | up to 4.0.15 | 1C1H3M0L |
| 4.0.2 | up to 4.0.10 | 1C2H3M0L |
| 4.0.0 | up to 4.0.2 | 2C2H2M0L |
| 3.11.18 | up to 4.0.0 | 0C0H0M0L |
| 3.11.12 | up to 3.11.18 | 0C1H0M0L |
| 3.11.10 | up to 3.11.12 | 1C1H0M0L |
| 3.11.8 | up to 3.11.10 | 1C2H0M0L |
| 3.11.0 | up to 3.11.8 | 1C2H1M0L |
| 3.1.0 | up to 3.11.0 | 0C1H0M0L |
| 3.0.31 | up to 3.1.0 | 0C0H0M0L |
| 3.0.26 | up to 3.0.31 | 0C1H0M0L |
| 3.0.24 | up to 3.0.26 | 1C1H0M0L |
| 3.0.22 | up to 3.0.24 | 1C2H0M0L |
| 3.0.0 | up to 3.0.22 | 1C2H1M0L |
| 2.2.20 | up to 3.0.0 | 0C0H0M0L |
| 2.2.18 | up to 2.2.20 | 0C1H0M0L |
| 2.2.0 | up to 2.2.18 | 0C1H1M0L |
| 2.1.23 | up to 2.2.0 | 0C0H0M0L |
| 2.1.22 | up to 2.1.23 | 0C1H0M0L |
| 2.1.0 | up to 2.1.22 | 0C1H1M0L |
| before 2.1.0 | all earlier versions | 0C0H1M0L |
No known vulnerabilities in 5.0.8-0 and later versions
Nothing in our data affects this version.
33 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.
Vulnerabilities · 10
| CVE | Severity | Published | Vulnerable | Fixed in |
|---|---|---|---|---|
| CVE-2026-47846Default superuser cassandra:cassandra left active when CASSANDRA_USER is customized | CRITICAL | 18 Jun 2026 | >=4.0.0, <4.0.20-0>=4.1.0, <4.1.11-0>=5.0.0, <5.0.8-0 | 4.0.20-04.1.11-05.0.8-0 |
| CVE-2026-27315Apache Cassandra has sensitive Information Leak in cqlsh | MEDIUM | 7 Apr 2026 | >=4.0.0, <4.0.20 | 4.0.20 |
| CVE-2025-26467org.apache.cassandra:cassandra-all: Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions (4.0.16 only) | HIGH | 25 Aug 2025 | >=4.0.16, <4.0.17 | 4.0.17 |
| CVE-2025-24860org.apache.cassandra:cassandra-all: Apache Cassandra: CassandraNetworkAuthorizer and CassandraCIDRAuthorizer can be bypassed allowing access to different network regions | MEDIUM | 4 Feb 2025 | >=4.0.0, <4.0.16>=4.1.0, <4.1.8>=5.0.0, <5.0.3 | 4.0.164.1.85.0.3 |
| CVE-2024-27137org.apache.cassandra:cassandra-all: Apache Cassandra: unrestricted deserialization of JMX authentication credentials | MEDIUM | 4 Feb 2025 | >=4.0.2, <4.0.15>=4.1.0, <4.1.8>=5.0.0, <5.0.3 | 4.0.154.1.85.0.3 |
| CVE-2025-23015org.apache.cassandra:cassandra-all: Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions | HIGH | 4 Feb 2025 | >=3.0.0, <3.0.31>=3.1.0, <3.11.18>=4.0.0, <4.0.16>=4.1.0, <4.1.8>=5.0.0, <5.0.3 | 3.0.313.11.184.0.164.1.85.0.3 |
| CVE-2023-30601Apache Cassandra: Privilege escalation when enabling FQL/Audit logs | HIGH | 30 May 2023 | >=4.0.0, <4.0.10>=4.1.0, <4.1.2 | 4.0.104.1.2 |
| CVE-2021-44521cassandra: RCE for scripted UDFs | CRITICAL | 11 Feb 2022 | >=3.0.0, <3.0.26>=3.11.0, <3.11.12>=4.0.0, <4.0.2 | 3.0.263.11.124.0.2 |
| CVE-2020-17516cassandra: internode encryption enforcement vulnerability | HIGH | 3 Feb 2021 | >=2.1.0, <2.1.23>=2.2.0, <2.2.20>=3.0.0, <3.0.24>=3.11.0, <3.11.10 | 2.1.232.2.203.0.243.11.10 |
| CVE-2020-13946cassandra: allows manipulation of the RMI registry to perform a MITM attack and capture user names and passwords used to access the JMX interface | MEDIUM | 1 Sep 2020 | <2.1.22>=2.2.0, <2.2.18>=3.0.0, <3.0.22>=3.11.0, <3.11.8 | 2.1.222.2.183.0.223.11.8 |
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.