CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-73504

CVE-2026-73504: Plaintext Authentication Token Exposure in cassandra-jdbc-wrapper Debug Logs

Amit Schendel
Amit Schendel
Senior Security Researcher

Nov 19, 2026·9 min read·0 visits

Executive Summary (TL;DR)

An incomplete log redaction routine in cassandra-jdbc-wrapper versions prior to 4.16.4 and 5.0.2 writes plaintext authentication tokens (such as DataStax Astra DB tokens) to application logs when DEBUG logging is active.

CVE-2026-73504 (GHSA-jc42-994r-vvwp) is a credential exposure vulnerability in ING Bank's cassandra-jdbc-wrapper (com.ing.data:cassandra-jdbc-wrapper). Resulting from an incomplete remediation of AIKIDO-2024-10565, the log sanitization routines in DriverUtil redact the password property but fail to redact the token property. When DEBUG logging is enabled, connection properties and JDBC URLs containing DataStax Astra DB bearer tokens are written in plaintext to application logs, enabling local users or log aggregation readers to harvest active database credentials.

Vulnerability Overview

The cassandra-jdbc-wrapper library (com.ing.data:cassandra-jdbc-wrapper), maintained by ING Bank, provides a JDBC-compliant API abstraction over the official DataStax Java driver for Apache Cassandra. It allows Java applications to establish connections, manage sessions, and execute CQL statements against Apache Cassandra clusters and DataStax Astra DB cloud instances using standard JDBC connection strings and java.util.Properties objects.

CVE-2026-73504 (also tracked as GHSA-jc42-994r-vvwp) is an information disclosure vulnerability classified under CWE-532 (Insertion of Sensitive Information into Log File). The flaw affects the connection initialization and session tracking logic within the com.ing.data.cassandra.jdbc.SessionHolder and com.ing.data.cassandra.jdbc.utils.DriverUtil classes. When an application operates with DEBUG level logging enabled for the JDBC driver namespace, the library outputs connection metadata—including the full JDBC connection URL and connection property maps—to the configured logging sink.

This vulnerability exists due to an incomplete patch for a prior credential exposure vulnerability tracked as AIKIDO-2024-10565. While the prior remediation introduced utility methods to mask the password parameter before emitting debug log statements, it omitted the token parameter (JdbcUrlUtil.TAG_TOKEN). Consequently, applications connecting to DataStax Astra DB or token-authenticated Cassandra clusters write active bearer tokens in cleartext to local log files, container standard output streams, or centralized log management infrastructure.

An adversary with local filesystem access, container log view permissions, or read access to centralized logging platforms (such as Elasticsearch, Splunk, or AWS CloudWatch) can extract these unredacted tokens. Possession of a valid authentication token allows the attacker to authenticate directly to the target Cassandra database and access or modify data within the permission scope of the compromised credential.

Root Cause Analysis

The root cause of CVE-2026-73504 is an incomplete denylist implementation in the credential redaction helper methods inside com.ing.data.cassandra.jdbc.utils.DriverUtil. To address AIKIDO-2024-10565, the maintainers implemented two static sanitization methods: toStringWithoutSensitiveValues(final Properties properties) and redactSensitiveValuesInJdbcUrl(final String jdbcUrl). These methods are invoked by SessionHolder whenever a session is acquired, opened, or released while DEBUG logging is active.

Both sanitization methods rely on explicit key matching against hardcoded constant values defined in JdbcUrlUtil. Prior to the patch for CVE-2026-73504, these methods only checked for the presence of JdbcUrlUtil.TAG_PASSWORD (which resolves to the string literal "password"). When a match was found in the Properties object or in the query parameter string of a JDBC URL, the value was replaced with the placeholder string "***".

However, cassandra-jdbc-wrapper supports multiple authentication schemes, including token-based authentication required for cloud-hosted DataStax Astra DB deployments. When connecting to Astra DB using a Secure Connect Bundle or cloud endpoint, credentials are frequently passed via the token key (JdbcUrlUtil.TAG_TOKEN), formatted as AstraCS:<client_id>:<client_secret>, either inside the Properties map passed to DriverManager.getConnection() or as a query string parameter in the JDBC URL (jdbc:cassandra://...&token=AstraCS:...).

Because TAG_TOKEN was excluded from the conditional checks in both toStringWithoutSensitiveValues() and redactSensitiveValuesInJdbcUrl(), the redaction routine treated the token property as non-sensitive metadata. In toStringWithoutSensitiveValues(), the shallow copy of the Properties object retained the cleartext token value prior to invoking Properties.toString(). Similarly, in redactSensitiveValuesInJdbcUrl(), the stream filter splitting parameters on the & delimiter failed to match parameters starting with "token=", returning the raw key-value pair untouched to the log output.

Code Analysis & Patch Evaluation

The vulnerability resides in src/main/java/com/ing/data/cassandra/jdbc/utils/DriverUtil.java. In the vulnerable versions (4.x prior to 4.16.4 and 5.x prior to 5.0.2), the sanitization methods inspected only TAG_PASSWORD:

// Vulnerable implementation in DriverUtil.java
public static String toStringWithoutSensitiveValues(final Properties properties) {
    final Properties withRedactedSensitiveValues = new Properties();
    withRedactedSensitiveValues.putAll(properties);
    if (withRedactedSensitiveValues.containsKey(TAG_PASSWORD)) {
        withRedactedSensitiveValues.setProperty(TAG_PASSWORD, "***");
    }
    // Vulnerability: TAG_TOKEN is not checked or overwritten
    return withRedactedSensitiveValues.toString();
}
 
public static String redactSensitiveValuesInJdbcUrl(final String jdbcUrl) {
    return Arrays.stream(jdbcUrl.split("&"))
        .map(param -> {
            if (param.startsWith(TAG_PASSWORD + "=")) {
                return TAG_PASSWORD + "=***";
            }
            // Vulnerability: parameters starting with TAG_TOKEN + "=" are returned unmodified
            return param;
        })
        .collect(Collectors.joining("&"));
}

The maintainers addressed this issue in commit ace58f7cf5c981d8dfe302f1a514ae4c6f827f38 (for the 5.x branch) and backported the fix in commit 0b7ea0322e538304119f58f1214e4171312b245b (for the 4.x branch). The patch imports JdbcUrlUtil.TAG_TOKEN and adds explicit conditional checks for the token property in both methods:

--- a/src/main/java/com/ing/data/cassandra/jdbc/utils/DriverUtil.java
+++ b/src/main/java/com/ing/data/cassandra/jdbc/utils/DriverUtil.java
@@ -54,6 +54,7 @@ import java.util.stream.Collectors;
 
 import static com.ing.data.cassandra.jdbc.utils.JdbcUrlUtil.TAG_PASSWORD;
+import static com.ing.data.cassandra.jdbc.utils.JdbcUrlUtil.TAG_TOKEN;
 import static com.ing.data.cassandra.jdbc.utils.WarningConstants.DRIVER_PROPERTY_NOT_FOUND;
 import static com.ing.data.cassandra.jdbc.utils.WarningConstants.URL_REDACTION_FAILED;
 import static org.apache.commons.collections4.ListUtils.emptyIfNull;
@@ -315,6 +316,9 @@ public static String toStringWithoutSensitiveValues(final Properties properties)
         if (withRedactedSensitiveValues.containsKey(TAG_PASSWORD)) {
             withRedactedSensitiveValues.setProperty(TAG_PASSWORD, "***");
         }
+        if (withRedactedSensitiveValues.containsKey(TAG_TOKEN)) {
+            withRedactedSensitiveValues.setProperty(TAG_TOKEN, "***");
+        }
         return withRedactedSensitiveValues.toString();
     }
 
@@ -341,6 +345,9 @@ public static String redactSensitiveValuesInJdbcUrl(final String jdbcUrl) {
                     if (param.startsWith(TAG_PASSWORD + "=")) {
                         return TAG_PASSWORD + "=***";
                     }
+                    if (param.startsWith(TAG_TOKEN + "=")) {
+                        return TAG_TOKEN + "=***";
+                    }
                     return param;
                 })
                 .collect(Collectors.joining("&"));

Along with the functional changes in DriverUtil.java, unit tests were added to src/test/java/com/ing/data/cassandra/jdbc/UtilsUnitTest.java to verify that both password and token (tested using the sample format AstraCS:SECRET_TOKEN_VALUE_1234567890) are replaced with *** while preserving non-sensitive parameters like user.

> [!NOTE] > Fix Completeness Assessment: While the patch prevents standard token and password disclosures, the architecture remains reliant on a static, case-sensitive denylist and basic string splitting. Several edge-case bypass vectors exist: > 1. URL-First-Parameter Boundary Bug: In redactSensitiveValuesInJdbcUrl(), the URL is split exclusively on the & character (jdbcUrl.split("&")). If token or password is placed as the first query parameter right after the ? delimiter (e.g., jdbc:cassandra://host:9042/ks?token=AstraCS:123&user=test), the first element of the split array is jdbc:cassandra://host:9042/ks?token=AstraCS:123. Because this string does not start with "token=", param.startsWith(TAG_TOKEN + "=") evaluates to false, leaving the token unredacted in the logs. > 2. Case Sensitivity and URL Encoding: startsWith and Properties.containsKey perform exact, case-sensitive matching. Any case variation (e.g., Token=) or percent-encoded parameter name (e.g., %74oken=) will bypass the check. > 3. Other Sensitive Parameters: Secrets used by auxiliary wrapper features—such as SSL keystore/truststore passwords or AWS SigV4 credentials—are not included in the denylist.

Exploitation Methodology

Exploitation of CVE-2026-73504 is passive and relies on post-compromise or insider access to log outputs (mapped to MITRE ATT&CK technique T1552.001: Unsecured Credentials: Credentials In Files). The primary prerequisite is that the target Java application uses a vulnerable version of cassandra-jdbc-wrapper, authenticates via the token property, and has DEBUG logging enabled for the com.ing.data.cassandra.jdbc logger hierarchy.

DEBUG logging is commonly enabled in staging environments, CI/CD test runners, or production deployments undergoing troubleshooting. When a connection is established through SessionHolder, the library emits entries matching the following format to the configured SLF4J backend:

DEBUG c.i.d.c.jdbc.SessionHolder - Opening connection to: jdbc:cassandra://dbaas---cluster1.apps.astra.datastax.com:9042/main_ks?user=token&token=AstraCS:AbCdEf1234567890:9876543210fedcba...
DEBUG c.i.d.c.jdbc.SessionHolder - Session acquired with properties: {user=token, token=AstraCS:AbCdEf1234567890:9876543210fedcba..., keyspace=main_ks}

An attacker with read permissions on the host filesystem, container log outputs (docker logs or kubectl logs), build artifacts, or a centralized SIEM/log aggregation platform can harvest these tokens using standard text search utilities or query filters:

# Searching local or mounted container log files for exposed Astra tokens
grep -RnE "(token=|AstraCS:)[A-Za-z0-9_:-]+" /var/log/app/

Once extracted, the AstraCS:... token can be used immediately from an external network position (provided the database endpoint is publicly reachable, as is default for DataStax Astra DB endpoints unless IP access lists are enforced) to authenticate via cqlsh, the DataStax DevOps/Data REST APIs, or the Cassandra Java driver.

Impact Assessment

CVE-2026-73504 is assigned a CVSS v3.1 base score of 5.5 (Medium) with the vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. The Attack Vector is scored as Local (AV:L) with Low Privileges Required (PR:L) because the vulnerability itself does not grant unauthenticated remote access to the logs; the attacker must already possess a foothold or read permissions within the environment hosting the log files or log management pipeline.

Attack Complexity is Low (AC:L) and requires no User Interaction (UI:N). Whenever DEBUG logging is active, every connection acquisition event deterministically outputs the token. The direct impact of the vulnerability is rated High for Confidentiality (C:H), with Integrity (I:N) and Availability (A:N) rated as None in the context of the information disclosure itself.

However, the downstream impact of compromising a live Cassandra or DataStax Astra DB authentication token frequently extends beyond confidentiality. In Astra DB deployments, tokens are bound to specific IAM roles (such as Database Administrator or R/W User). If an application uses a read-write or administrative token, an attacker who harvests the token from the logs gains the ability to exfiltrate sensitive tables, modify or delete production data, drop keyspaces, or alter schema definitions.

Furthermore, because log files are regularly forwarded to centralized aggregation tiers and retained in cold storage backups for compliance, exposed long-lived tokens remain vulnerable to retrospective harvesting long after DEBUG logging has been turned off on the application host.

Remediation & Mitigation

To remediate CVE-2026-73504, upgrade com.ing.data:cassandra-jdbc-wrapper to version 4.16.4 (for the 4.x release train) or 5.0.2 (for the 5.x release train) or later. Update the dependency declaration in pom.xml (Maven) or build.gradle (Gradle) accordingly:

<!-- Maven pom.xml configuration for 5.x branch -->
<dependency>
    <groupId>com.ing.data</groupId>
    <artifactId>cassandra-jdbc-wrapper</artifactId>
    <version>5.0.2</version>
</dependency>

> [!WARNING] > Due to the URL splitting limitation in redactSensitiveValuesInJdbcUrl(), even after upgrading to 4.16.4 or 5.0.2, avoid placing token= or password= as the first query parameter immediately following the ? delimiter in a raw JDBC URL string. Pass sensitive credentials via the Properties map argument in DriverManager.getConnection(url, props) instead.

If an immediate dependency upgrade is not feasible, implement the following compensating controls:

  1. Disable Debug Logging: Ensure the logging framework (Logback, Log4j2, etc.) explicitly sets the log level for com.ing.data.cassandra.jdbc to INFO or WARN in all environments:
<!-- logback.xml mitigation -->
<configuration>
    <logger name="com.ing.data.cassandra.jdbc" level="INFO" />
    <logger name="com.ing.data.cassandra.jdbc.SessionHolder" level="WARN" />
</configuration>
  1. Rotate Potentially Exposed Tokens: If an unpatched application was executed with DEBUG logging enabled while using token-based authentication, consider the token compromised. Revoke the token immediately in the DataStax Astra DB administration console or Cassandra authentication backend and provision a new credential.

  2. Purge and Mask Historical Logs: Audit log storage repositories and SIEM indices for entries containing AstraCS: or token=. Implement ingestion-pipeline scrubbing rules (e.g., in Fluentd, Vector, or Logstash) using regular expressions (s/(token=)[^&,\s}]+/$1***/g) to redact sensitive strings before indexing.

Official Patches

ING Bank (GitHub Advisory)Official GitHub Security Advisory GHSA-jc42-994r-vvwp
ING Bank (Release v4.16.4)Patched release v4.16.4 for 4.x branch
ING Bank (Release v5.0.2)Patched release v5.0.2 for 5.x branch

Fix Analysis (2)

Technical Appendix

CVSS Score
5.5/ 10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected Systems

com.ing.data:cassandra-jdbc-wrapper (Maven / Java)

Affected Versions Detail

Product
Affected Versions
Fixed Version
cassandra-jdbc-wrapper (4.x Branch)
ING Bank
< 4.16.44.16.4
cassandra-jdbc-wrapper (5.x Branch)
ING Bank
>= 5.0.0, < 5.0.25.0.2
AttributeDetail
CVE / Advisory IDCVE-2026-73504 / GHSA-jc42-994r-vvwp
Weakness ClassCWE-532 (Insertion of Sensitive Information into Log File)
CVSS v3.1 Score5.5 Medium (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)
Attack VectorLocal / Log File & SIEM Read Access
Affected Packagecom.ing.data:cassandra-jdbc-wrapper (< 4.16.4, 5.0.0 - 5.0.1)
Patched Versions4.16.4 and 5.0.2
Exploit / KEV StatusNo known public exploits; Not listed in CISA KEV

MITRE ATT&CK Mapping

T1552.001Unsecured Credentials: Credentials In Files
Credential Access
CWE-532
Insertion of Sensitive Information into Log File

The product generates log files that contain sensitive information such as credentials, cryptographic keys, or proprietary data that should not be visible to unauthorized entities.

Vulnerability Timeline

Maintainer Maxime Wiewiora commits token redaction fixes to 4.x and 5.x branches
2026-07-07
Patched versions v4.16.4 and v5.0.2 released on GitHub and Maven Central
2026-07-08
GitHub Security Advisory GHSA-jc42-994r-vvwp and CVE-2026-73504 formally published
2026-11-18
OSV database updated with affected version and commit ranges
2026-11-19

References & Sources

  • [1]GitHub Security Advisory GHSA-jc42-994r-vvwp
  • [2]Fix Commit (4.x Branch - 0b7ea0322e538304119f58f1214e4171312b245b)
  • [3]Fix Commit (5.x / Master Branch - ace58f7cf5c981d8dfe302f1a514ae4c6f827f38)
  • [4]cassandra-jdbc-wrapper Release v4.16.4
  • [5]cassandra-jdbc-wrapper Release v5.0.2
  • [6]NVD CVE-2026-73504 Detail
  • [7]CVE.org Record: CVE-2026-73504
  • [8]CVE List V5 JSON Record

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•about 1 hour ago•CVE-2026-76088
7.5

CVE-2026-76088: Unbounded Compressed Packet Descent Denial of Service in PGPainless

A denial-of-service vulnerability (CWE-400) exists in PGPainless versions prior to 1.7.8 and 2.0.x prior to 2.0.4 within the MessageInspector and InlineDetachImpl components. These components manually iterate over OpenPGP packet streams without enforcing the global 16-layer maximum nesting limit (MAX_LAYER_DEPTH). An unauthenticated remote attacker can supply a specially crafted OpenPGP message containing deeply nested PGPCompressedData packets to trigger unbounded recursive decompression, resulting in CPU starvation and Java Virtual Machine (JVM) heap exhaustion.

Amit Schendel
Amit Schendel
2 views•8 min read
•about 2 hours ago•CVE-2026-69138
6.5

CVE-2026-69138: Authorization Bypass Through User-Controlled Key and Missing Authorization in djangocms-versioning

An authorization bypass and broken object-level access control vulnerability exists in djangocms-versioning prior to version 2.6.1. The check_discard and check_edit_redirect condition pipelines on the Version model omitted the user_can_change permission predicate. Because the corresponding administrative views retrieve target versions directly by their URL primary key and depend entirely on these condition pipelines for object-level access control, authenticated staff users without per-object change permissions can permanently delete draft versions or spawn new draft versions from published content.

Alon Barad
Alon Barad
2 views•10 min read
•about 3 hours ago•CVE-2026-69131
4.3

CVE-2026-69131: Missing Authorization in django-filer Bulk Deletion Admin Action

A missing authorization vulnerability exists in django-filer versions prior to 3.5.0 when the optional per-folder permission system (FILER_ENABLE_PERMISSIONS) is enabled. The bulk delete admin action (delete_files_or_folders) verifies global Django model-level deletion permissions but fails to enforce object-level FolderPermission edit checks. Consequently, an authenticated staff user holding model-level delete rights can delete files, folders, and directory trees from folders where their access has been explicitly restricted to read-only via FolderPermission.

Alon Barad
Alon Barad
3 views•9 min read
•about 4 hours ago•CVE-2026-75506
6.6

CVE-2026-75506: Second-Order OS Command Injection in OliveTin shellAfterCompleted Hook

CVE-2026-75506 (GHSA-vc6p-m6vx-6cwq) is a second-order OS command injection vulnerability in OliveTin affecting versions 3000.0.0 prior to 3000.18.1. The post-execution hook mechanism, shellAfterCompleted, interpolates runtime execution outputs and username variables directly into a shell command string passed to sh -c without validation. When an action emits untrusted output containing shell metacharacters, those metacharacters break out of the intended syntax and execute arbitrary OS commands under the context of the OliveTin service process.

Alon Barad
Alon Barad
4 views•10 min read
•about 5 hours ago•CVE-2026-71481
7.5

CVE-2026-71481: Cryptographic Signature Verification Bypass in ALTCHA PHP Library

CVE-2026-71481 (GHSA-82w8-65qw-gch6) is a cryptographic signature verification bypass (CWE-347) in the altcha-org/altcha PHP library affecting versions 2.0.0 through 2.0.2. Due to a flawed conditional check in the verifySolution method, omitting the signature field from a submitted challenge payload causes the server to skip HMAC verification entirely, even when a server-side HMAC secret is configured. Unauthenticated remote attackers can exploit this flaw to self-issue low-difficulty Proof-of-Work challenges, solve them with trivial effort, and bypass CAPTCHA controls.

Alon Barad
Alon Barad
4 views•10 min read
•about 8 hours ago•CVE-2026-61618
6.9

CVE-2026-61618: Improper Input Validation of KZG Accumulator Limbs in snark-verifier

CVE-2026-61618 (GHSA-265x-v3qf-ff6p) is an improper input validation vulnerability (CWE-20) in Axiom Crypto's snark-verifier library prior to version 0.2.5. The library decodes KZG accumulator public-instance limbs without enforcing canonical bit-width bounds prior to elliptic curve coordinate reconstruction. In the Ethereum Virtual Machine (EVM) loader path, the generated Yul bytecode validates that reconstructed affine coordinates lie on the elliptic curve, but fails to verify that the constituent limbs respect their allocated bit-widths, allowing non-canonical proof representations. In the native Rust execution path, accumulator decoding relies on unchecked assertions and unwraps, allowing malformed public instances to trigger an unhandled process panic.

Amit Schendel
Amit Schendel
4 views•12 min read