CVE-2026-40946: Github.com/oxia db/oxia Oxia Has An OIDC Token Vulnerability

CRITICAL
Advisory Identifier: GHSA-fhvp-9hcj-6m33
CWE-287
Published
Advisory Summary

CVE-2026-40946 is a CRITICAL oxia has an oidc token vulnerability (CWE-287: Improper Authentication) affecting Github.com/oxia db/oxia libraries in the Go ecosystem. The issue involves oxia has an oidc token audience validation bypass via skipclientidcheck. Remediation is available by upgrading affected packages to version 0.16.2.

CVE-2026-40946 at a Glance

CVE Identifier CVE-2026-40946
GHSA Identifier GHSA-fhvp-9hcj-6m33
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-287: Improper Authentication
Affected Product Github.com/oxia db/oxia
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-40946

To remediate this vulnerability, upgrade all affected Github.com/oxia db/oxia dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/oxia-db/oxia fixed: 0.16.2
Upgrade github.com/oxia-db/oxia to 0.16.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/oxia-db/oxia

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-40946, inspect your project dependencies for Github.com/oxia db/oxia:

inspect dependencies for github.com/oxia-db/oxia

Analyze the terminal output to locate any version of Github.com/oxia db/oxia in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.16.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Github.com/oxia db/oxia, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

CVE-2026-40946 Affected Github.com/oxia db/oxia Versions

1 component(s)
Fixed Versions:
0.16.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/oxia-db/oxia
Go
< 0.16.2
0.16.2

References

Frequently Asked Questions

What is CVE-2026-40946?
CVE-2026-40946 is a security vulnerability in Github.com/oxia db/oxia involving Oxia has an OIDC token audience validation bypass via SkipClientIDCheck under CWE-287: Improper Authentication.
Which Github.com/oxia db/oxia versions are affected?
Affected versions include releases prior to 0.16.2 across affected packages: github.com/oxia-db/oxia.
What version fixes CVE-2026-40946?
Upgrading to 0.16.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/oxia-db/oxia affected?
Yes, github.com/oxia-db/oxia is affected in releases prior to 0.16.2. Upgrade your dependency to 0.16.2 or later.
What CWE is associated with CVE-2026-40946?
CVE-2026-40946 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check Go dependencies for CVE-2026-40946?
Run the dependency tree command: 'inspect dependencies for github.com/oxia-db/oxia'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fhvp-9hcj-6m33",
  "modified" : "2026-04-24T20:39:53Z",
  "published" : "2026-04-14T23:14:49Z",
  "aliases" : [ "CVE-2026-40946" ],
  "summary" : "Oxia has an OIDC token audience validation bypass via SkipClientIDCheck",
  "details" : "### Summary\nThe 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.\n\n### Impact\nIn 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.\n\nAll versions using OIDC authentication are affected.\n\n### Details\nIn `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.\n\n### Patches\nFixed by removing `SkipClientIDCheck: true` and setting the `ClientID` field from the configured `AllowedAudiences`.\n\n### Workarounds\nEnsure network-level isolation so that only trusted services can reach the Oxia gRPC endpoints.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/oxia-db/oxia"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.16.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.16.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/oxia-db/oxia/security/advisories/GHSA-fhvp-9hcj-6m33"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-40946"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/oxia-db/oxia"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-14T23:14:49Z",
    "nvd_published_at" : "2026-04-21T22:16:20Z"
  }
}