Information Exposure Through Log Files Affecting cassandra-4.0-cis-hardened package, versions <4.0.20-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (4th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Information Exposure Through Log Files vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-CASSANDRA40CISHARDENED-15994336
  • published12 Apr 2026
  • disclosed7 Apr 2026

Introduced: 7 Apr 2026

NewCVE-2026-27315  (opens in a new tab)
CWE-532  (opens in a new tab)

How to fix?

Upgrade Minimos:latest cassandra-4.0-cis-hardened to version 4.0.20-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cassandra-4.0-cis-hardened package and not the cassandra-4.0-cis-hardened package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.