Unauthenticated user impersonation via SAML signature verification
Published Oct 1, 2026 · Updated Oct 1, 2026
Improper SAML signature verification in Apache APISIX 3.17.0 through 3.18.0 allows remote attackers to impersonate users on saml-auth routes. The saml-auth login flow inadequately verifies the signature on a SAML response; the precise validation error has not been publicly described. Exposure requires a route protected by the plugin, whose affected default configuration permits impersonation of any user on that route.
Summary
What happened
Improper SAML signature verification in Apache APISIX 3.17.0 through 3.18.0 allows remote attackers to impersonate users on saml-auth routes. The saml-auth login flow inadequately verifies the signature on a SAML response; the precise validation error has not been publicly described. Exposure requires a route protected by the plugin, whose affected default configuration permits impersonation of any user on that route.
The record
- CVE
- CVE-2026-94212
- Published
- Oct 1, 2026
- Updated
- Oct 1, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache APISIX
- Classifications
- T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 1, 2026CVE publishedPublication date reported by the CVE source.
- Oct 1, 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=3.17.0 <=3.18.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started