Quick answers
- Is CVE-2026-94212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94212 being exploited in the wild.
- How severe is CVE-2026-94212?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- Apache APISIX 3.17.0 through 3.18.0.
- Is there a fix for CVE-2026-94212?
- Yes: fixed in Apache APISIX 3.19.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-94212 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-94212?
- 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: Apache APISIX 3.19.0
Technical details
The saml-auth plugin in Apache APISIX fails to properly verify cryptographic signatures on SAML assertions under default configuration. An unauthenticated network attacker can craft malicious SAML tokens that bypass signature validation, allowing impersonation of any user. This affects versions 3.17.0 through 3.18.0, and is fixed in version 3.19.0.
Affected products
- Apache APISIX 3.17.0 through 3.18.0
Timeline
- 2026-10-01: disclosed