<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 03:46:09 +0000</lastBuildDate>
    <item>
      <title>BIT-cassandra-2026-27315 — Apache Cassandra: cqlsh history sensitive information leak</title>
      <link>https://cve.radiocsirt.org/vuln/bit-cassandra-2026-27315</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: 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; Bitnami: 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://cve.radiocsirt.org/vuln/bit-cassandra-2026-27315</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-DD05788 — Security fixes for CVE-2018-10237, CVE-2020-8908, CVE-2021-41973, CVE-2022-24823, CVE-2022-3171, CVE-2022-3509, CVE-202…</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-dd05788</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: stargate&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the stargate package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: stargate&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the stargate package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-dd05788</guid>
    </item>
    <item>
      <title>EUVD-2026-290217</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-290217</link>
      <description>EUVD-2026-290217</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-290217</guid>
    </item>
    <item>
      <title>fkie_cve-2026-27315</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27315</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-27315</guid>
    </item>
    <item>
      <title>GHSA-fh34-c629-p8xj — Apache Cassandra has sensitive Information Leak in cqlsh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fh34-c629-p8xj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.cassandra:cassandra-all&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; Maven: org.apache.cassandra:cassandra-all&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://cve.radiocsirt.org/vuln/ghsa-fh34-c629-p8xj</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1009 — Apache Cassandra: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1009</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache Cassandra ausnutzen, um seine Privilegien zu erhöhen, um Informationen offenzulegen, und um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache Cassandra ausnutzen, um seine Privilegien zu erhöhen, um Informationen offenzulegen, und um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1009</guid>
    </item>
  </channel>
</rss>
