Quick answers
- Is CVE-2026-94276 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94276 being exploited in the wild.
- How severe is CVE-2026-94276?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- Apache APISIX 3.12.0 through 3.18.0.
- Is there a fix for CVE-2026-94276?
- Yes: fixed in 3.19.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-94276 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-94276?
- Check whether you run Apache APISIX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.19.0
Technical details
The vulnerability exists in the openid-connect plugin's remote introspection logic when an authorization server serves multiple issuers. The plugin fails to properly validate that a token's issuer matches the expected issuer for a protected route, allowing tokens valid for one issuer to be accepted on routes restricted to another. This is an authentication bypass that requires an authenticated attacker with a valid token from an alternate issuer.
Affected products
- Apache APISIX 3.12.0 through 3.18.0
Timeline
- 2026-10-01: disclosed