github.com/oxia-db/oxia
Affected
- introduced
0, fixed0.16.2(semver)
Fixed versions
0.16.2
Fix
- Fixed version
0.16.2go get github.com/oxia-db/[email protected]
Advisory
Also known as: CVE-2026-40945, GO-2026-5546
Oxia exposes bearer token in debug log messages on authentication failure
Summary
When OIDC authentication fails, the full bearer token is logged at DEBUG level in plaintext. If debug logging is enabled in production, JWT tokens are exposed in application logs and any connected log aggregation system.
Impact
An attacker with access to application logs (e.g., via a compromised log aggregation pipeline, shared logging infrastructure, or misconfigured log access controls) can extract valid JWT tokens and replay them to authenticate as legitimate users.
All versions using OIDC authentication are affected.
Details
In oxiad/common/rpc/auth/interceptor.go, the validateTokenWithContext() function logs the complete token value via slog.String("token", token) when authentication fails. This includes the full JWT header, payload, and signature.
Patches
Fixed by redacting the token in log output — only the last 8 characters are preserved for correlation purposes.
Workarounds
Ensure DEBUG-level logging is never enabled in production environments.
High Basis: The source's own band: HIGH
0, fixed 0.16.2 (semver)0.16.2
0.16.2go get github.com/oxia-db/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0