CVE-2026-73504: cassandra-jdbc-wrapper · Authentication Token Exposed in Logs
Affects com.ing.data:cassandra-jdbc-wrapperSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium : upgrade to 5.0.2 when convenient.
Data as of 19 Nov 2026, 01:51 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.5 |
|---|
- Patch
- Available – fixed in 5.0.2, 4.16.4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade com.ing.data:cassandra-jdbc-wrapper to 5.0.2; com.ing.data:cassandra-jdbc-wrapper to 4.16.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mavencom.ing.data:cassandra-jdbc-wrapper | Affected
| Fixed in
|
| Mavencom.ing.data:cassandra-jdbc-wrapper | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in cassandra-jdbc-wrapper versions 5.0.2 and 4.16.4 that addresses this issue by properly redacting the 'token' property in logs. Users should upgrade to these fixed versions to prevent token leakage. Until patched, avoid enabling DEBUG logging in production or sensitive environments where token exposure could occur.
Description
The cassandra-jdbc-wrapper library versions prior to 5.0.2 and before 4.16.4 improperly log authentication tokens in plaintext when DEBUG logging is enabled. The vulnerability stems from redaction helpers that only mask the 'password' property but fail to redact the equally sensitive 'token' property used for token-based authentication, such as with DataStax Astra. This results in authentication tokens being exposed in application logs, potentially compromising cluster access.
References
- github.com/ing-bank/cassandra-jdbc-wrapper/security/advisories/GHSA-jc42-994r-vvwp (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-73504 (opens in a new tab)
- github.com/ing-bank/cassandra-jdbc-wrapper/commit/0b7ea0322e538304119f58f1214e4171312b245b (opens in a new tab)
- github.com/ing-bank/cassandra-jdbc-wrapper/commit/ace58f7cf5c981d8dfe302f1a514ae4c6f827f38 (opens in a new tab)
- github.com/ing-bank/cassandra-jdbc-wrapper (opens in a new tab)
- github.com/ing-bank/cassandra-jdbc-wrapper/releases/tag/v4.16.4 (opens in a new tab)
- github.com/ing-bank/cassandra-jdbc-wrapper/releases/tag/v5.0.2 (opens in a new tab)