How severe is GHSA-fh34-c629-p8xj?

No CVSS score has been assigned to GHSA-fh34-c629-p8xj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fh34-c629-p8xj?

GHSA-fh34-c629-p8xj affects the following packages: org.apache.cassandra:cassandra-all (Maven). Ecosystems affected: Maven.

How do I fix GHSA-fh34-c629-p8xj?

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

How do I detect GHSA-fh34-c629-p8xj 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-fh34-c629-p8xj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-fh34-c629-p8xj?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fh34-c629-p8xj can be triaged on real exposure rather than presence alone.

Is GHSA-fh34-c629-p8xj actively exploited in the wild?

No public exploit code has been indexed for GHSA-fh34-c629-p8xj 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-fh34-c629-p8xj?

GHSA-fh34-c629-p8xj has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th 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-fh34-c629-p8xj?

GHSA-fh34-c629-p8xj is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fh34-c629-p8xj published, and has it been updated?

GHSA-fh34-c629-p8xj was published on April 7, 2026 and was last updated on April 9, 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

GHSA-fh34-c629-p8xj — cassandra-all

GHSA-fh34-c629-p8xj is a CWE-532 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.

Apache Cassandra has sensitive Information Leak in cqlsh

Also known asBIT-cassandra-2026-27315CVE-2026-27315

Published

Apr 7, 2026

Updated

Apr 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-fh34-c629-p8xj.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕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

Users are recommended to upgrade to version 4.0.20, which fixes this issue.

-- Description: Cassandra's command-line tool, cqlsh, provides a command history feature that allows users to recall previously executed commands using the up/down arrow keys. These history records are saved in the ~/.cassandra/cqlsh_history file in the user's home directory.

However, cqlsh does not redact sensitive information when saving command history. This means that if a user executes operations involving passwords (such as logging in or creating users) within cqlsh, these passwords are permanently stored in cleartext in the history file on the disk.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.cassandra:cassandra-all`	≥ 4.0&&< 4.0.20	4.0.20`org.apache.cassandra:cassandra-all:4.0.20`

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.0.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fh34-c629-p8xj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fh34-c629-p8xj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-fh34-c629-p8xj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Sensitive Information Leak in cqlsh in Apache Cassandra 4.0 allows access to sensitive information, like passwords, from previously executed cqlsh command via ~/.cassandra/cqlsh_history local file access. Users are recommended to upgrade to version 4.0.20, which fixes this issue. -- Description: Cassandra's command-line tool, cqlsh, provides a command history feature that allows users to recall previously executed commands using the up/down arrow keys. These history records are saved in the ~/.cassandra/cqlsh_history file in the user's home directory. However, cqlsh does not redact sensiti

O3 Security · Impact-Aware SCA

Is GHSA-fh34-c629-p8xj in your dependencies?

O3 Security finds GHSA-fh34-c629-p8xj across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works