cve.bz

CVE-2026-73504 cassandra-jdbc-wrapper: Authentication Token Exposed in Logs

5.5 mediumEPSS 0.2%Fix available

Medium (5.5) in ing-bank cassandra-jdbc-wrapper. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in com.ing.data:cassandra-jdbc-wrapper 4.16.4, 5.0.2.

On this page
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.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • com.ing.data:cassandra-jdbc-wrapper (Maven): fixed in 5.0.2, 4.16.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-73504 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73504?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73504?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-73504 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ing-bank cassandra-jdbc-wrapper< 4.16.4
ing-bank cassandra-jdbc-wrapper>= 5.0.0, < 5.0.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jc42-994r-vvwpMavencom.ing.data:cassandra-jdbc-wrapper>=5.0.0 <5.0.25.0.2
GHSA-jc42-994r-vvwpMavencom.ing.data:cassandra-jdbc-wrapper<4.16.44.16.4

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • googlesky/CVE-2026-73504 Harbor Check: matches CVE 0 stars, Python, created
    cassandra-jdbc-wrapper <4.16.4: DriverUtil redaction helpers added for password logging only redact TAG_PASSWORD — the live Astra auth toke…

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON