Bearer-token disclosure via failed-authentication debug logging
Published Apr 21, 2026 · Updated Apr 21, 2026
Sensitive information exposure in Oxia before 0.16.2 allows attackers with log access to recover bearer tokens from failed OIDC authentication. The validateTokenWithContext() function in oxiad/common/rpc/auth/interceptor.go passes the entire rejected token to slog.String() instead of redacting it. OIDC and DEBUG logging must be enabled, and log access is required; a recovered valid JWT can be replayed as its legitimate user.
Summary
What happened
Sensitive information exposure in Oxia before 0.16.2 allows attackers with log access to recover bearer tokens from failed OIDC authentication. The validateTokenWithContext() function in oxiad/common/rpc/auth/interceptor.go passes the entire rejected token to slog.String() instead of redacting it. OIDC and DEBUG logging must be enabled, and log access is required; a recovered valid JWT can be replayed as its legitimate user.
The record
- CVE
- CVE-2026-40945
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- Oxia
- Product
- Oxia
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.16.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo