CVE-2026-40945

Description

### 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.

How to fix CVE-2026-40945

To remediate CVE-2026-40945, upgrade the affected package to a fixed version below.

• —upgrade to 0.16.2 or later

Is CVE-2026-40945 being exploited?

Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• from 0, < 0.16.2

CVSS scores

References (4)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-40945
• PATCHgithub.com/oxia-db/oxia
• WEBgithub.com/oxia-db/oxia/commit/f7259d0ebc739fc95ff19f93c823433850857416
• WEBgithub.com/oxia-db/oxia/security/advisories/GHSA-pm7q-rjjx-979p