Password disclosure via unredacted command history
Published Apr 7, 2026 · Updated Apr 7, 2026
Sensitive information exposure in Apache Cassandra cqlsh 4.0 through 4.0.19 allows local users to read stored passwords from command history. The save_history function passes the entire readline buffer to write_history_file without filtering password-bearing commands. Exposure requires readable access to another user's history after that user entered credentials, and disclosed passwords can enable account access.
Summary
What happened
Sensitive information exposure in Apache Cassandra cqlsh 4.0 through 4.0.19 allows local users to read stored passwords from command history. The save_history function passes the entire readline buffer to write_history_file without filtering password-bearing commands. Exposure requires readable access to another user's history after that user entered credentials, and disclosed passwords can enable account access.
The record
- CVE
- CVE-2026-27315
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Cassandra
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.0 <=4.0.19
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo