CVE-2026-40945: 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.
Published Apr 14, 2026 · Updated Apr 24, 2026
Affected packages
github.com/oxia-db/oxia
- Ecosystem
- Go
- Affected
- <= 0.16.1
- Fixed in
- 0.16.2
- Check
go list -m github.com/oxia-db/oxia
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-40943
Oxia affected by server crash via race condition in session heartbeat handling
high8.7Apr 14, 2026CVE-2026-40944
Oxia's TLS CA certificate chain validation fails with multi-certificate PEM bundles
high8.0Apr 14, 2026CVE-2026-40946
Oxia has an OIDC token audience validation bypass via SkipClientIDCheck
critical9.3Apr 14, 2026
