<?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, 22 Nov 2026 19:27:32 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-408969</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-408969</link>
      <description>EUVD-2026-408969</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-408969</guid>
    </item>
    <item>
      <title>fkie_cve-2026-73504</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-73504</link>
      <description>&lt;p&gt;cassandra-jdbc-wrapper provides a JDBC-compliant API over the Java driver for Apache Cassandra. Prior to 4.16.4 and 5.0.2, DriverUtil.toStringWithoutSensitiveValues() and DriverUtil.redactSensitiveValuesInJdbcUrl() redact the password property but not the equally sensitive token property used for DataStax Astra and other token-based authentication. When DEBUG logging is enabled, SessionHolder passes connection properties and JDBC URLs containing token through these helpers, causing the live token to be written in plaintext when connections are acquired or released. An attacker who can read those logs can use the token to access Cassandra data and operations authorized to that credential. This issue is fixed in versions 4.16.4 and 5.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;cassandra-jdbc-wrapper provides a JDBC-compliant API over the Java driver for Apache Cassandra. Prior to 4.16.4 and 5.0.2, DriverUtil.toStringWithoutSensitiveValues() and DriverUtil.redactSensitiveValuesInJdbcUrl() redact the password property but not the equally sensitive token property used for DataStax Astra and other token-based authentication. When DEBUG logging is enabled, SessionHolder passes connection properties and JDBC URLs containing token through these helpers, causing the live token to be written in plaintext when connections are acquired or released. An attacker who can read those logs can use the token to access Cassandra data and operations authorized to that credential. This issue is fixed in versions 4.16.4 and 5.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-73504</guid>
    </item>
    <item>
      <title>GHSA-jc42-994r-vvwp — cassandra-jdbc-wrapper: Authentication Token Exposed in Logs</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jc42-994r-vvwp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.ing.data:cassandra-jdbc-wrapper&lt;/p&gt;
&lt;p&gt;### Summary
The fix for [AIKIDO-2024-10565](https://intel.aikido.dev/cve/AIKIDO-2024-10565) (plaintext password logging) introduced two
redaction helpers — `DriverUtil.toStringWithoutSensitiveValues()` and
`DriverUtil.redactSensitiveValuesInJdbcUrl()` — but both helpers only redact
the `&amp;#34;password&amp;#34;` property/parameter (`JdbcUrlUtil.TAG_PASSWORD`). The equally
sensitive `&amp;#34;token&amp;#34;` property (`JdbcUrlUtil.TAG_TOKEN`), used for DataStax
Astra and other token-based Cassandra authentication, is completely unredacted
by both helpers. Applications using token-based authentication with DEBUG
logging enabled will therefore log the live authentication token in plaintext
via `SessionHolder`&amp;#39;s calls to these same two helpers — the exact same
exposure pattern that the original fix was intended to prevent.&lt;/p&gt;
&lt;p&gt;### Details
**File:** `src/main/java/com/ing/data/cassandra/jdbc/utils/DriverUtil.java`&lt;/p&gt;
&lt;p&gt;```java
// toStringWithoutSensitiveValues (lines 341-347) -- only redacts &amp;#34;password&amp;#34;
public static String toStringWithoutSensitiveValues(final Properties properties) {
    final Properties withRedactedSensitiveValues = (Properties) properties.clone();
    if (withRedactedSensitiveValues.containsKey(TAG_PASSWORD)) {
        withRedactedSensitiveValues.setProperty(TAG_PASSWORD, &amp;#34;***&amp;#34;);
    }
    return withRedactedSensitiveValues.toString();
}&lt;/p&gt;
&lt;p&gt;// redactSensitiveValuesInJdbcUrl (lines 355-378) -- only redacts &amp;#34;password&amp;#34;
final String redactedQuery = Arrays.stream(...)
    .map(param -&amp;gt; {
        if (para…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.ing.data:cassandra-jdbc-wrapper&lt;/p&gt;
&lt;p&gt;### Summary
The fix for [AIKIDO-2024-10565](https://intel.aikido.dev/cve/AIKIDO-2024-10565) (plaintext password logging) introduced two
redaction helpers — `DriverUtil.toStringWithoutSensitiveValues()` and
`DriverUtil.redactSensitiveValuesInJdbcUrl()` — but both helpers only redact
the `&amp;#34;password&amp;#34;` property/parameter (`JdbcUrlUtil.TAG_PASSWORD`). The equally
sensitive `&amp;#34;token&amp;#34;` property (`JdbcUrlUtil.TAG_TOKEN`), used for DataStax
Astra and other token-based Cassandra authentication, is completely unredacted
by both helpers. Applications using token-based authentication with DEBUG
logging enabled will therefore log the live authentication token in plaintext
via `SessionHolder`&amp;#39;s calls to these same two helpers — the exact same
exposure pattern that the original fix was intended to prevent.&lt;/p&gt;
&lt;p&gt;### Details
**File:** `src/main/java/com/ing/data/cassandra/jdbc/utils/DriverUtil.java`&lt;/p&gt;
&lt;p&gt;```java
// toStringWithoutSensitiveValues (lines 341-347) -- only redacts &amp;#34;password&amp;#34;
public static String toStringWithoutSensitiveValues(final Properties properties) {
    final Properties withRedactedSensitiveValues = (Properties) properties.clone();
    if (withRedactedSensitiveValues.containsKey(TAG_PASSWORD)) {
        withRedactedSensitiveValues.setProperty(TAG_PASSWORD, &amp;#34;***&amp;#34;);
    }
    return withRedactedSensitiveValues.toString();
}&lt;/p&gt;
&lt;p&gt;// redactSensitiveValuesInJdbcUrl (lines 355-378) -- only redacts &amp;#34;password&amp;#34;
final String redactedQuery = Arrays.stream(...)
    .map(param -&amp;gt; {
        if (para…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jc42-994r-vvwp</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3079 — Gitea: Mehrere Schwachstellen ermöglichen Ausführen von beliebigem Programmcode</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3079</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder Denial-of-Service-Zustände zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder Denial-of-Service-Zustände zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3079</guid>
    </item>
  </channel>
</rss>
