Advisory record · GHSA-pm7q-rjjx-979p

Oxia exposes bearer token in debug log messages on authentication failure

CVSS 8.7 HighEPSS 0.0031 · 23rd percentile

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.

PackageEcosystemAffectedFixed in
github.com/oxia-db/oxiaGo<0.16.20.16.2
Identifiers
GHSA-pm7q-rjjx-979p · CVE-2026-40945 · GO-2026-5546
Weakness (CWE)
CWE-532
Published
14 Apr 2026
Updated
25 Jun 2026

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

ScoreRatingCVSSVectorSource
8.7 High 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 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

  1. 31 Oct 2026, 15:06 UTC First seen by agentprime
  2. 31 Oct 2026, 15:06 UTC Confirmed by OSV

Sources

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.