# CVE-2026-94276: Apache APISIX improper authentication in openid-connect plugin

Source: https://junglewise.ai/threats/cve-2026-94276-improper-authentication-vulnerability-in-apache-apisix-on-a-route  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-01. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-94276 · Severity: info · Published 2026-10-01

Apache APISIX is an API gateway that manages access to web services. The openid-connect authentication plugin can be configured to verify tokens through an external authorization server. An attacker with a valid token from one issuer can bypass authentication and gain unauthorized access to APIs restricted to a different issuer, potentially exposing sensitive data or services.

Technologies: [Apache APISIX](https://junglewise.ai/threats/technologies/apisix). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

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

## References

- [https://lists.apache.org/thread.html/txn3br25kl657fh15rwcy1oht1xbpyyk](https://lists.apache.org/thread.html/txn3br25kl657fh15rwcy1oht1xbpyyk)
- [http://www.openwall.com/lists/oss-security/2026/10/01/8](http://www.openwall.com/lists/oss-security/2026/10/01/8)

## Related threats

- [Apache APISIX authorization bypass via non-canonical URL paths](https://junglewise.ai/threats/cve-2026-94269-use-of-non-canonical-url-paths-for-authorization-decisions)
- [Apache APISIX batch-requests plugin uncontrolled resource allocation](https://junglewise.ai/threats/cve-2026-94250-allocation-of-resources-without-limits-or-throttling)
- [Apache APISIX feishu-auth and dingtalk-auth session fixation](https://junglewise.ai/threats/cve-2026-94220-cross-site-request-forgery-csrf-vulnerability-in-feishu-auth-and)
- [Apache APISIX cryptographic signature verification bypass in saml-auth](https://junglewise.ai/threats/cve-2026-94212-improper-verification-of-cryptographic-signature-vulnerability-in)
- [Apache APISIX session data persistence in authorization scope](https://junglewise.ai/threats/cve-2026-82806-exposure-of-data-element-to-wrong-session-vulnerability-in-apache)