Skip to main content
Menu
CVEs

CVE

cassandra-jdbc-wrapper auth token leak in DEBUG logs

CVE-2026-73504EUVD-2026-129173Published Updated Summary written by a model

5.5MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 4.16.4, 5.0.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.16.4, 5.0.2.

Summary

The cassandra-jdbc-wrapper software from ing-bank writes live authentication tokens in plaintext to its logs when DEBUG logging is enabled. A local user with low privileges who can read those logs could use a token to access Cassandra data and operations allowed for that credential.

Original description

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.

cve.now Index

21Pcve.now Index 21 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.5/10CVSS 5.5
  • No patch0/5No signal

What would change the score

  • Would score about 61 if added to CISA KEV
  • Would score about 56 if CISA's SSVC rates exploitation active
  • Would score about 43 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.16.4, 5.0.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-73504 (cassandra-jdbc-wrapper: Authentication Token Exposed in Logs), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-73504 (entry last updated 2026-11-18):
Affected:
- ing-bank cassandra-jdbc-wrapper: fixed in 4.16.4; from 5.0.0, fixed in 5.0.2
Fixed versions: 4.16.4, 5.0.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-73504 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-73504 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ing-bank/cassandra-jdbc-wrapper/security/advisories/GHSA-jc42-994r-vvwp
- https://github.com/ing-bank/cassandra-jdbc-wrapper/commit/0b7ea0322e538304119f58f1214e4171312b245b
- https://github.com/ing-bank/cassandra-jdbc-wrapper/commit/ace58f7cf5c981d8dfe302f1a514ae4c6f827f38
- https://github.com/ing-bank/cassandra-jdbc-wrapper/releases/tag/v4.16.4
- https://github.com/ing-bank/cassandra-jdbc-wrapper/releases/tag/v5.0.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-73504
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-73504"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • ing-bank cassandra-jdbc-wrapper

    fixed in 4.16.4; From 5.0.0 · fixed in 5.0.2

Evidence 7

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-73504

Is CVE-2026-73504 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-73504?

cassandra-jdbc-wrapper: before 4.16.4; from 5.0.0 before 5.0.2.Source: cve.now feed data

How do I fix CVE-2026-73504?

Upgrade to a fixed version: 4.16.4, 5.0.2.Source: cve.now feed data

More CVEs