Skip to main content
VulnerabilityPublished

CVE-2026-73504: ing-bank cassandra-jdbc-wrapper · Sensitive Data in Logs

Affects ing-bank cassandra-jdbc-wrapperSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 5.0.2 or 4.16.4 when convenient.

Data as of 18 Nov 2026, 20:06 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade ing-bank cassandra-jdbc-wrapper to 5.0.2 or 4.16.4.

Affected software

ProductAffectedFixed in
ing-bankcassandra-jdbc-wrapperAffected
  • >=5.0.0 <5.0.2
Fixed in
  • 5.0.2
ing-bankcassandra-jdbc-wrapperAffected
  • <4.16.4
Fixed in
  • 4.16.4

AI-suggested

Upgrade to cassandra-jdbc-wrapper versions 4.16.4 or 5.0.2 or later, where the token property is properly redacted in logs. Until upgraded, avoid enabling DEBUG logging in production environments or restrict access to logs to trusted personnel only to prevent token exposure.

Description

A vulnerability in ing-bank's cassandra-jdbc-wrapper prior to versions 4.16.4 and 5.0.2 causes sensitive token authentication data to be logged in plaintext when DEBUG logging is enabled. The issue arises because the token property used for DataStax Astra and other token-based authentication is not redacted in logs, unlike the password property. This exposure allows an attacker with access to logs to obtain tokens and potentially access Cassandra data and operations authorized by those tokens. The vulnerability is fixed in versions 4.16.4 and 5.0.2.

References

Community reviews

Loading reviews…