# Oxia exposes bearer token in debug log messages on authentication failure

Advisory record · `GHSA-pm7q-rjjx-979p`

- **Identifiers:** `GHSA-pm7q-rjjx-979p` · `CVE-2026-40945` · `GO-2026-5546`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-532](https://cwe.mitre.org/data/definitions/532.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 14 Apr 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Apr 2026, 23:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/oxia-db/oxia` (Go): affected `<0.16.2`; fixed in `0.16.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Oxia (github.com/oxia-db/oxia) versions before 0.16.2 write the full bearer token to debug logs when OIDC authentication fails. An attacker who can read application logs, such as through a compromised log aggregation pipeline or misconfigured log access, could take a valid JWT and reuse it to authenticate as a legitimate user. Upgrade to version 0.16.2, which redacts the token so only its last 8 characters are logged. Until then, make sure debug logging is never enabled in production.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.7 High, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0031, the 23rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:06 UTC: First seen by agentprime
- 31 Oct 2026, 15:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pm7q-rjjx-979p)

## Sources

- [GitHub Advisory Database: GHSA-pm7q-rjjx-979p](https://github.com/advisories/GHSA-pm7q-rjjx-979p)
- [OSV: GHSA-pm7q-rjjx-979p](https://osv.dev/vulnerability/GHSA-pm7q-rjjx-979p)
- <https://github.com/oxia-db/oxia/security/advisories/GHSA-pm7q-rjjx-979p>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-40945>
- <https://github.com/oxia-db/oxia/commit/f7259d0ebc739fc95ff19f93c823433850857416>
- <https://github.com/oxia-db/oxia>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-pm7q-rjjx-979p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pm7q-rjjx-979p/>. Everything for agents: <https://agentprime.io/llms.txt>.
