# CVE-2026-32588: Apache Cassandra: Authenticated DoS via ALTER ROLE Password Hashing > An authenticated user can cause denial of service in Apache Cassandra by repeatedly changing passwords, increasing query latencies. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Apr 2026 - **Updated:** 9 Apr 2026 - **Also known as:** AZL-82673, CLEANSTART-2026-AO49375, CLEANSTART-2026-LG69060, GHSA-qffm-gf3j-6mvg, MINI-f48g-fq73-fg87 ## What is CVE-2026-32588? CVE-2026-32588 is a medium-severity denial of service vulnerability in Apache Cassandra, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Authenticated DoS over CQL in Apache Cassandra 4.0, 4.1, 5.0 allows authenticated user to raise query latencies via repeated password changes. Users are recommended to upgrade to version 4.0.20, 4.1.11, 5.0.7, which fixes this issue. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2026-32588? 6 open source packages ship an affected version, including org.apache.cassandra:cassandra-all. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.cassandra:cassandra-all` | Maven | From 4.0 | 4.0.20 | | `org.apache.cassandra:cassandra-all` | Maven | From 4.0 | 4.0.20 | | `org.apache.cassandra:cassandra-all` | Maven | From 4.1 | 4.1.11 | | `org.apache.cassandra:cassandra-all` | Maven | From 4.1 | 4.1.11 | | `org.apache.cassandra:cassandra-all` | Maven | From 5.0 | 5.0.7 | | `org.apache.cassandra:cassandra-all` | Maven | From 5.0 | 5.0.7 | Products: Apache Cassandra. ## How do I fix CVE-2026-32588? Upgrade org.apache.cassandra:cassandra-all to a fixed version for your release line: 4.0.20, 4.1.11 or 5.0.7. ## Is CVE-2026-32588 being exploited? There is no known exploitation of CVE-2026-32588 in the wild and no public exploit code. ## Other vulnerabilities in Apache Cassandra - [CVE-2016-3427](https://insights.sbomify.com/CVE-2016-3427/): Oracle Java SE and JRockit Unspecified (critical 9.8, exploited in the wild) - [CVE-2018-8016](https://insights.sbomify.com/CVE-2018-8016/): Missing Authentication for Critical Function in Apache Cassandra (critical 9.8) - [CVE-2021-44521](https://insights.sbomify.com/CVE-2021-44521/): Remote code execution for scripted UDFs (critical 9.1) - [CVE-2026-27314](https://insights.sbomify.com/CVE-2026-27314/): Apache Cassandra: Privilege escalation via ADD IDENTITY authorization bypass (high 8.8) - [CVE-2025-26467](https://insights.sbomify.com/CVE-2025-26467/): Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions (4.0.16 only) (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32588 and fix it if it is affected. What it is: CVE-2026-32588 is a medium-severity denial of service vulnerability in Apache Cassandra, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-32588 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.cassandra:cassandra-all (Maven): affected from 4.0; fixed in 4.0.20 - org.apache.cassandra:cassandra-all (Maven): affected from 4.0; fixed in 4.0.20 - org.apache.cassandra:cassandra-all (Maven): affected from 4.1; fixed in 4.1.11 - org.apache.cassandra:cassandra-all (Maven): affected from 4.1; fixed in 4.1.11 - org.apache.cassandra:cassandra-all (Maven): affected from 5.0; fixed in 5.0.7 - org.apache.cassandra:cassandra-all (Maven): affected from 5.0; fixed in 5.0.7 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-32588/ (Markdown: https://insights.sbomify.com/CVE-2026-32588/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32588 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32588 - OSV: https://osv.dev/vulnerability/CVE-2026-32588 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32588/ Summaries are generated and may contain mistakes; the official description above is the record.