# Apache Cassandra: Privilege escalation when enabling FQL/Audit logs

Advisory record · `GHSA-m9p2-j4hg-g373`

- **Identifiers:** `GHSA-m9p2-j4hg-g373` · `BIT-cassandra-2023-30601` · `CVE-2023-30601`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-269](https://cwe.mitre.org/data/definitions/269.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md)
- **Published:** 6 Jul 2023
- **Updated:** 7 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Jul 2023, 21:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.cassandra:cassandra-all` (Maven): affected `>=4.1.0, <4.1.2 || >=4.0.0, <4.0.10`; fixed in `4.1.2`, `4.0.10`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Cassandra cassandra-all versions 4.0.0 through 4.0.9 and 4.1.0 through 4.1.1 are affected by a privilege escalation issue when FQL or audit logging is enabled. A user with JMX access can run arbitrary commands as the user running Cassandra. Upgrade to 4.0.10 or 4.1.2, and keep the new allow_nodetool_archive_command setting at false. Until then, restrict nodetool and JMX access to trusted users only.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (apache)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 28th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:19 UTC: First seen by agentprime
- 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m9p2-j4hg-g373)

## Sources

- [GitHub Advisory Database: GHSA-m9p2-j4hg-g373](https://github.com/advisories/GHSA-m9p2-j4hg-g373)
- [OSV: GHSA-m9p2-j4hg-g373](https://osv.dev/vulnerability/GHSA-m9p2-j4hg-g373)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-30601>
- <https://github.com/apache/cassandra/commit/22d74c711658507addfd67e2c78b04a9b88413b2>
- <https://github.com/apache/cassandra/commit/aafb4d19448f12ce600dc4e84a5b181308825b32>
- <https://github.com/apache/cassandra>
- <https://issues.apache.org/jira/browse/CASSANDRA-18550>
- <https://lists.apache.org/thread/f74p9jdhmmp7vtrqd8lgm8bq3dhxl8vn>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m9p2-j4hg-g373>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m9p2-j4hg-g373/>. Everything for agents: <https://agentprime.io/llms.txt>.
