Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A09:2025 - Security Logging & Alerting Failures
ASVS 5.0
V16 - Security Logging and Error Handling Log data sanitization
|
| Impact | This vulnerability presents a nuanced risk profile. The CVSS 3.1 score of 5.5 reflects local attack vector (AV:L), low complexity (AC:L), and low privilege requirements (PR:L), with high confidentiality impact (C:H) but no integrity or availability impact. However, the EPSS score of 0.02% (percentile 4%) indicates extremely low likelihood of exploitation in the wild, suggesting limited practical weaponization despite the technical feasibility. The attack requires local file system access and existing user privileges, making it most relevant in multi-tenant hosting, shared development environments, or scenarios where user isolation is weak. No CISA KEV status or public proof-of-concept provided in the input, indicating this is not confirmed actively exploited. The vulnerability is primarily a lateral privilege escalation or credential theft risk post-compromise rather than a primary attack vector, making it lower priority than remote code execution or unauthenticated information disclosure vulnerabilities, though still material for compliance and defense-in-depth in sensitive deployments. |
| Exploit ScenarioDerived | A low-privileged local user gains access to a shared development server running Cassandra 4.0.15. The user browses another developer's home directory and reads ~/.cassandra/cqlsh_history, recovering database admin credentials from a CREATE USER command executed earlier in the day. The attacker uses these credentials to connect directly to the Cassandra cluster and extract sensitive data from a production backup database stored on the same server. This scenario is feasible due to the low complexity (AV:L/AC:L) and low privilege requirement (PR:L), and occurs frequently in multi-tenant cloud environments or shared lab infrastructure, although the overall EPSS of 0.02% suggests exploitation remains uncommon in practice. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 07, 2026
Apache Cassandra 4.0 through 4.0.19 stores cleartext passwords and other sensitive command history in the ~/.cassandra/cqlsh_history file without redaction, allowing local authenticated users to extract credentials via direct file access. Vendor-released patch available in version 4.0.20; exploitation requires local file system access and existing user privileges but poses significant risk in multi-tenant or shared system environments.
RemediationAI
Vendor-released patch: Upgrade Apache Cassandra to version 4.0.20 or later, which implements redaction of sensitive information in the cqlsh_history file. For immediate mitigation on systems that cannot be upgraded immediately, restrict file system permissions on the ~/.cassandra/cqlsh_history file to prevent unprivileged local user access (chmod 600), and audit existing history files for exposed credentials using log scanning tools. Users should manually clear history files if they contain known sensitive commands: remove or truncate ~/.cassandra/cqlsh_history after a suspected exposure event. See Apache Cassandra JIRA CASSANDRA-21180 and the security mailing list thread (references provided) for additional patch details and timeline.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The cqlsh command-line interface for Apache Cassandra implements a command history feature that persists user-executed commands to a plaintext history file in the user's home directory. The underlying technology involves readline-style history management (CWE-532: Insertion of Sensitive Information into Log File), where no sanitization or redaction mechanism is applied before writing to disk. Affected products include Apache Cassandra versions 4.0 through 4.0.19, identified by CPE references to Apache Cassandra 4.0.x release branches. The vulnerability stems from inadequate output encoding and failure to implement sensitive data filtering in the history logging subsystem, allowing passwords from CREATE USER, ALTER USER, LOGIN, and similar authentication-related commands to persist in cleartext alongside normal query history.
Know when Cassandra gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Primary rating from Vendor (apache) · only source for this CVE.
CVSS VectorVendor: apache
Lifecycle Timeline
2DescriptionCVE.org
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 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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Unspecified vulnerability in Oracle Java SE 6u113, 7u99, and 8u77; Java SE Embedded 8u77; and JRockit R28.3.9 allows rem
The default configuration in Apache Cassandra 3.8 through 3.11.1 binds an unauthenticated JMX/RMI interface to all netwo
handler/ssl/OpenSslEngine.java in Netty 4.0.x before 4.0.37.Final and 4.1.x before 4.1.1.Final allows remote attackers t
Privilege Defined With Unsafe Actions vulnerability in Apache Cassandra. Rated high severity (CVSS 8.8), this vulnerabil
Privilege Defined With Unsafe Actions vulnerability in Apache Cassandra. Rated high severity (CVSS 8.8), this vulnerabil
Privilege escalation when enabling FQL/Audit logs allows user with JMX access to run arbitrary commands as the user runn
The default configuration in Apache Cassandra 1.2.0 through 1.2.19, 2.0.0 through 2.0.13, and 2.1.0 through 2.1.3 binds
Authenticated denial of service via CQL in Apache Cassandra 4.0 through 5.0 allows authenticated users to elevate query
In Apache Cassandra, all versions prior to 2.1.22, 2.2.18, 3.0.22, 3.11.8 and 4.0-beta2, it is possible for a local atta
Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: RMI). Rated medium severity (C
Incorrect Authorization vulnerability in Apache Cassandra allowing users to access a datacenter or IP/CIDR groups they s
In Apache Cassandra it is possible for a local attacker without access to the Apache Cassandra process or configuration
EUVD-2026-19763
GHSA-fh34-c629-p8xj
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB