What is the CVSS score of CVE-2026-27315?

CVE-2026-27315 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Is there a patch available for CVE-2026-27315?

Yes, a patch is available for CVE-2026-27315. Update the affected software to the latest version immediately.

Apache CVE-2026-27315

EUVD-2026-19763 MEDIUM

Insertion of Sensitive Information into Log File (CWE-532)

2026-04-07 security@apache.org

GHSA-fh34-c629-p8xj

Apache Information Disclosure

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Patch released

Apr 09, 2026 - 02:30 nvd

Patch available

EUVD ID Assigned

Apr 07, 2026 - 17:22 euvd

EUVD-2026-19763

Analysis Generated

Apr 07, 2026 - 17:22 vuln.today

CVE Published

Apr 07, 2026 - 17:16 nvd

MEDIUM 5.5

DescriptionCVE.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.

AnalysisAI

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.

Technical ContextAI

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.

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.