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-2026-73504
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2026-11-19. A secondary CVSS source baseline 5.5; sources differ by 0.0.
Also known asEUVD-2026-129173 (ENISA EUVD) · GHSA-jc42-994r-vvwp (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 5.5
- EG Score
- 5.5MEDIUMhigh confidence
- EG Risk
- 41EG Risk 41/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity55% × 45%Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 15th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 18, 2026
Last Modified
November 18, 2026
Advisory Details (5)
Auto-updated Nov 18, 20265.0.2
Patch available: ing-bank/cassandra-jdbc-wrapper v5.0.2
https://github.com/ing-bank/cassandra-jdbc-wrapper/releases/tag/v5.0.24.16.4
Patch available: ing-bank/cassandra-jdbc-wrapper v4.16.4
https://github.com/ing-bank/cassandra-jdbc-wrapper/releases/tag/v4.16.4commit ace58f7cf5c9 (ing-bank/cassandra-jdbc-wrapper)
Patch available: ing-bank/cassandra-jdbc-wrapper v4.16.4 (contains commit ace58f7cf5c9)
https://github.com/ing-bank/cassandra-jdbc-wrapper/commit/ace58f7cf5c981d8dfe302f1a514ae4c6f827f38commit 0b7ea0322e53 (ing-bank/cassandra-jdbc-wrapper)
Patch available: ing-bank/cassandra-jdbc-wrapper v5.0.2 (contains commit 0b7ea0322e53)
https://github.com/ing-bank/cassandra-jdbc-wrapper/commit/0b7ea0322e538304119f58f1214e4171312b245bIncomplete Fix for AIKIDO-2024-10565: Authentication Token Exposed in Logs · Advisory · ing-bank/cassandra-jdbc-wrapper · GitHub
https://github.com/ing-bank/cassandra-jdbc-wrapper/security/advisories/GHSA-jc42-994r-vvwpVendor Advisories for CVE-2026-73504(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| maven | com.ing.data:cassandra-jdbc-wrapper @ 5.0.2 (fixes >= 5.0.0, < 5.0.2) | — | ghsa |
| maven | com.ing.data:cassandra-jdbc-wrapper @ 4.16.4 (fixes <= 4.16.3) | — | ghsa |
These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-11-19 01:46 UTCEchelonGraph re-scored
- 2026-11-19 01:46 UTCGHSA enrichmentGHSA-jc42-994r-vvwp · GitHub severity MODERATE · GitHub CVSS 5.5
- 2026-11-18 21:42 UTCEchelonGraph re-scored
- 2026-11-18 21:28 UTCEchelonGraph re-scored
- 2026-11-18 21:03 UTCENISA EUVD ID recordedEUVD-2026-129173 · Source: ENISA EUVD
- 2026-11-18 20:58 UTCEchelonGraph re-scored
- 2026-11-18 20:28 UTCEchelonGraph re-scored
- 2026-11-18 19:58 UTCEchelonGraph re-scoredFirst assessed: 5.5 MEDIUM
- 2026-11-18 19:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-73504?
When was the CVE record for CVE-2026-73504 published?
Is CVE-2026-73504 actively exploited?
What is the CVSS score of CVE-2026-73504?
How do I remediate CVE-2026-73504?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-73504
Is Your Infrastructure Affected by CVE-2026-73504?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.