CVE-2026-40946

Oxia: OIDC token audience validation bypass via SkipClientIDCheck

Published Apr 21, 2026 CVSS 4.0 · 9.2 Critical EPSS < 1% KEV · Not listed
Description
Oxia is a metadata store and coordination system. Prior to 0.16.2, 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. This vulnerability is fixed in 0.16.2.

Analysis

AI-generated

Technical impact

The vulnerability in Oxia’s OIDC authentication provider allows the SkipClientIDCheck flag to be set to true, effectively disabling audience claim validation. This means any token issued by the same OIDC issuer for unrelated services can be accepted by Oxia, permitting an attacker to impersonate legitimate users or services and gain unauthorized access. The identified weakness corresponds to CWE‑287, which concerns authentication bypass by failing to verify identity information properly.

Affected Systems

Oxia installations from versions prior to 0.16.2 are affected. The product is the Oxia metadata store and coordination system provided by oxia-db:oxia. Users running any older minor release that has not incorporated the 0.16.2 update are vulnerable.

Risk and Exploitability

With a CVSS score of 9.2, this issue is considered of high severity. EPSS data is not available, but the vulnerability is not yet listed in CISA KEV. The likely attack vector is remote, where an adversary obtains or forges an OIDC token from the same issuer and presents it to Oxia. Because the standard audience check is bypassed, such a token would be accepted without further validation, enabling elevation of privilege or unauthorized access to the datastore.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Oxia to version 0.16.2 or later, where the SkipClientIDCheck flag is removed and audience claim validation is enforced.
  • Ensure that your OIDC provider issues tokens with the correct audience claim that matches Oxia’s client identifier and validate this claim during authentication.
  • If custom verifier configuration is used, explicitly disable SkipClientIDCheck or remove any configuration that overrides the default audience validation logic.

Generated by OpenCVE AI on April 22, 2026 at 06:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-fhvp-9hcj-6m33 Oxia has an OIDC token audience validation bypass via SkipClientIDCheck
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Oxia-db
Oxia-db oxia
Vendors & Products Oxia-db
Oxia-db oxia
Type Values Removed Values Added
Description Oxia is a metadata store and coordination system. Prior to 0.16.2, 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. This vulnerability is fixed in 0.16.2.
Title Oxia: OIDC token audience validation bypass via SkipClientIDCheck
Weaknesses CWE-287
References
Metrics cvssV4_0

{'score': 9.2, 'vector': '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Apr 22, 2026, 6:11 PM
Reserved
Apr 15, 2026, 8:40 PM
Status
Deferred
Published
Apr 21, 2026, 10:16 PM
Modified
Jun 17, 2026, 10:45 AM