CVE-2026-40945

描述

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

如何修補 CVE-2026-40945

要修補 CVE-2026-40945,請將受影響套件升級到下列已修補版本。

• —升級至 0.16.2 或更新版本

CVE-2026-40945 正在被利用嗎?

低 — EPSS 為 0.1%,目前沒有觀察到大規模利用活動。

受影響套件(1)

• from 0, < 0.16.2

CVSS 分數

參考連結(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