Advisory

GHSA-fhvp-9hcj-6m33

Also known as: CVE-2026-40946, GO-2026-5364

Summary

Oxia has an OIDC token audience validation bypass via SkipClientIDCheck

Details

Summary
The OIDC authentication provider unconditionally sets SkipClientIDCheck: true in the go-oidc verifier configuration, disabling the standard audience (aud) claim validation at the library level. This allows tokens issued for unrelated services by the same OIDC issuer to be accepted by Oxia.

Impact
In deployments using OIDC authentication, an attacker possessing a valid JWT token issued by the same identity provider but intended for a different service (different client_id/aud) can authenticate to Oxia. This bypasses the intended audience isolation of OAuth2/OIDC.

All versions using OIDC authentication are affected.

Details
In oxiad/common/rpc/auth/oidc.go, both createStaticKeyVerifier() and createRemoteVerifier() set SkipClientIDCheck: true. While a custom audience check exists in Authenticate(), the library-level check — which validates the aud claim against the expected client_id — is completely bypassed.

Patches
Fixed by removing SkipClientIDCheck: true and setting the ClientID field from the configured AllowedAudiences.

Workarounds
Ensure network-level isolation so that only trusted services can reach the Oxia gRPC endpoints.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-04-14 23:14 UTC
Modified
2026-06-25 19:56 UTC

Affected packages and fixes

github.com/oxia-db/oxia

Go · All systems

Affected

  • introduced 0, fixed 0.16.2 (semver)

Fixed versions

0.16.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences