ing-bank · Gitea · published 2026-11-18
CVE-2026-73504cassandra-jdbc-wrapper: Authentication Token Exposed in Logs
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-73504 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 15% of all CVEs. This Gitea vulnerability: CVSS 5.5 (v3.1). Fixed upstream in Gitea 1.27.3. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 1.27.3.
Patch events
DevOpsGitea
Gitea security release: 1.27.3
Upgrade to
1.27.3Why: CVE-2026-73504: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (15th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.5 (v3.1)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- ing-bank cassandra-jdbc-wrapper
< 4.16.4(affected)>= 5.0.0, < 5.0.2(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.