Authentication bypass via disabled OIDC audience validation
Published Apr 21, 2026 · Updated Apr 21, 2026
Authentication bypass in Oxia before 0.16.2 allows remote attackers to access the service with an OIDC token meant for another audience. The OIDC provider sets SkipClientIDCheck in both verifier constructors, preventing go-oidc from comparing the aud claim with the configured client ID. Exploitation requires OIDC authentication and a valid JWT from the same issuer for another client, which authenticates the token holder to reachable Oxia gRPC endpoints.
Summary
What happened
Authentication bypass in Oxia before 0.16.2 allows remote attackers to access the service with an OIDC token meant for another audience. The OIDC provider sets SkipClientIDCheck in both verifier constructors, preventing go-oidc from comparing the aud claim with the configured client ID. Exploitation requires OIDC authentication and a valid JWT from the same issuer for another client, which authenticates the token holder to reachable Oxia gRPC endpoints.
The record
- CVE
- CVE-2026-40946
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- Oxia
- Product
- Oxia
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.16.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo