Answer in brief
CVE-2026-73504 records a Medium severity (CVSS 5.5) vulnerability in cassandra-jdbc-wrapper: Authentication Token Exposed in Logs. The current sources do not mark it as known exploited. The current feed maps ing-bank/cassandra-jdbc-wrapper (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ing-bank/cassandra-jdbc-wrapper (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ing-bank/cassandra-jdbc-wrappergeneric | <4.16.4 || >=5.0.0 <5.0.2 | 4.16.4, 5.0.2 |
Published upstream
Nov 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.