<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 20:38:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-27315 — Apache Cassandra: cqlsh history sensitive information leak</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-27315</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Cassandra&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 4.0.20, which fixes this issue.&lt;/p&gt;
&lt;p&gt;--
Description: Cassandra&amp;#39;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&amp;#39;s home directory.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Cassandra&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 4.0.20, which fixes this issue.&lt;/p&gt;
&lt;p&gt;--
Description: Cassandra&amp;#39;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&amp;#39;s home directory.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-27315</guid>
    </item>
  </channel>
</rss>
