Summary
Oxia exposes bearer token in debug log messages on authentication failure
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.
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.
Workarounds
Ensure DEBUG-level logging is never enabled in production environments.
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fixed by redacting the token in log output, only the last 8 characters are preserved for correlation purposes.
Frequently Asked Questions
- What is CVE-2026-40945? CVE-2026-40945 is a high-severity security vulnerability in github.com/oxia-db/oxia (go), affecting versions <= 0.16.1. It is fixed in 0.16.2.
- Which versions of github.com/oxia-db/oxia are affected by CVE-2026-40945? github.com/oxia-db/oxia (go) versions <= 0.16.1 is affected.
- Is there a fix for CVE-2026-40945? Yes. CVE-2026-40945 is fixed in 0.16.2. Upgrade to this version or later.
- Is CVE-2026-40945 exploitable, and should I be worried? Whether CVE-2026-40945 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-40945 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-40945? Upgrade
github.com/oxia-db/oxiato 0.16.2 or later.