How severe is GHSA-m9p2-j4hg-g373?

GHSA-m9p2-j4hg-g373 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-m9p2-j4hg-g373?

GHSA-m9p2-j4hg-g373 affects the following packages: org.apache.cassandra:cassandra-all (Maven), org.apache.cassandra:cassandra-all (Maven). Ecosystems affected: Maven.

How do I fix GHSA-m9p2-j4hg-g373?

Update org.apache.cassandra:cassandra-all to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m9p2-j4hg-g373 is resolved across your whole dependency graph.

How do I detect GHSA-m9p2-j4hg-g373 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cassandra:cassandra-all, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m9p2-j4hg-g373 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is GHSA-m9p2-j4hg-g373 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m9p2-j4hg-g373 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m9p2-j4hg-g373?

GHSA-m9p2-j4hg-g373 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 28th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m9p2-j4hg-g373?

GHSA-m9p2-j4hg-g373 is classified as Improper Privilege Management (CWE-269). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m9p2-j4hg-g373 published, and has it been updated?

GHSA-m9p2-j4hg-g373 was published on July 6, 2023 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

Apache Cassandra: Privilege escalation when enabling FQL/Audit logsGHSA-m9p2-j4hg-g373

HIGHFix: apache/cassandra@22d74c7

GHSA-m9p2-j4hg-g373 is a high-severity (CVSS 7.8) Improper Privilege Management vulnerability in org.apache.cassandra:cassandra-all. A fix is available for org.apache.cassandra:cassandra-all — see the affected versions and patch details below.

Also known asBIT-cassandra-2023-30601CVE-2023-30601

Published

Jul 6, 2023

Updated

Aug 7, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m9p2-j4hg-g373.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.apache.cassandra:cassandra-all☕org.apache.cassandra:cassandra-all

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

WORKAROUND The vulnerability requires nodetool/JMX access to be exploitable, disable access for any non-trusted users.

MITIGATION Upgrade to 4.0.10 or 4.1.2 and leave the new FQL/Auditlog configuration property allow_nodetool_archive_command as false.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.cassandra:cassandra-all`	≥ 4.1.0&&< 4.1.2	4.1.2`org.apache.cassandra:cassandra-all:4.1.2`
☕Maven	`org.apache.cassandra:cassandra-all`	≥ 4.0.0&&< 4.0.10	4.0.10`org.apache.cassandra:cassandra-all:4.0.10`

Affected Products

1 product · 2 configurations

Application

cassandraapache

≥ 4.1.0 && < 4.1.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cassandra:cassandra-all, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.cassandra:cassandra-all to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m9p2-j4hg-g373 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

Privilege escalation when enabling FQL/Audit logs allows user with JMX access to run arbitrary commands as the user running Apache Cassandra This issue affects Apache Cassandra: from 4.0.0 through 4.0.9, from 4.1.0 through 4.1.1. WORKAROUND The vulnerability requires nodetool/JMX access to be exploitable, disable access for any non-trusted users. MITIGATION Upgrade to 4.0.10 or 4.1.2 and leave the new FQL/Auditlog configuration property allow_nodetool_archive_command as false.

O3 Security · Impact-Aware SCA

Is GHSA-m9p2-j4hg-g373 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.8/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-269Improper Privilege Management

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jul 6, 2023

Last updated

Aug 7, 2026

Identifiers

GHSA-m9p2-j4hg-g373

BIT-cassandra-2023-30601

References

Advisorynvd.nist.gov · CVE 2023 30601 Webgithub.com · 22d74c711658507addfd67e2c78b04a9b88413b2 Webgithub.com · aafb4d19448f12ce600dc4e84a5b181308825b32 Webissues.apache.org · CASSANDRA 18550 Weblists.apache.org · f74p9jdhmmp7vtrqd8lgm8bq3dhxl8vn Packagegithub.com · cassandra

Related vulnerabilities

This CVE is high severity; 4 of 8 other CVEs affecting cassandra-all are rated as high or higher (top: high).

CVE-2026-27315CVE-2026-32588CVE-2026-27314CVE-2025-26467CVE-2025-24860CVE-2024-27137CVE-2025-23015CVE-2023-30601

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 7, 2026

Apache Cassandra: Privilege escalation when enabling FQL/Audit logsGHSA-m9p2-j4hg-g373

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-m9p2-j4hg-g373 in your dependencies?