Advisory record · GHSA-fhvp-9hcj-6m33

Oxia has an OIDC token audience validation bypass via SkipClientIDCheck

CVSS 9.2 CriticalCriticalEPSS 0.0032 · 25th percentile

Critical, because:

  • CVSS score 9.2: 9.0 or more.

How we decide what’s critical

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-fhvp-9hcj-6m33 · CVE-2026-40946 · GO-2026-5364
Weakness (CWE)
CWE-287
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 (Go module github.com/oxia-db/oxia) versions before 0.16.2 are affected. In deployments using OIDC authentication, an attacker holding a valid JWT issued by the same identity provider for a different service can authenticate to Oxia, because the audience check is disabled. Upgrade to 0.16.2. If upgrading is not possible, limit access to the Oxia gRPC endpoints to trusted services at the network level.

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
9.2 Critical 4.0 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0032, the 25th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 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.