Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach saml-auth-protected route
-
DeliveryForge SAML assertion asserting target user
-
ExploitSubmit assertion with invalid/unverified signature
-
ExecutionPlugin accepts, issues session as victim
-
ImpactAccess protected upstream as impersonated user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | Requires the target Apache APISIX gateway to run an affected version (3.17.0 through 3.18.0) with the saml-auth plugin enabled on one or more routes - notably the DEFAULT configuration of this plugin is vulnerable, so no additional misconfiguration is needed. Exploitation is unauthenticated and requires no user interaction per the description (though the vendor's CVSS 4.0 vector states PR:L, a conflict to verify). Limiting factors: the narrow version window (only two minor releases) and the fact that only routes actually protected by saml-auth are affected; deployments not using saml-auth, or already on 3.19.0+, are not exposed. |
| Impact | This is a genuine high-priority authentication-bypass issue despite the moderate 6.4 vendor score. The description explicitly states an UNAUTHENTICATED attacker can impersonate ANY user on EVERY route protected by the saml-auth plugin under DEFAULT configuration - a complete SAML SSO authentication bypass via improper cryptographic signature verification (CWE-347). This conflicts with the vendor CVSS 4.0 vector, which uses PR:L (attacker needs some privilege); the prose clearly describes PR:N, so the vendor vector likely understates reach - verify with Apache. The vendor also scores impact only on the subsequent system (VC/VI/VA:N on the gateway but SC:H/SI:H on the protected upstreams), which is reasonable for a gateway but, combined with PR:L, pulls the 4.0 score down to 6.4; a PR:N impersonation of arbitrary users (potentially including privileged accounts) on protected backends is materially more severe. No EPSS score, no CISA KEV listing, and no public exploit were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The narrow affected window (only 3.17.0 through 3.18.0) limits the exposed population, but the 'default configuration' qualifier means vulnerable deployments need no special misconfiguration - any affected version running saml-auth is exposed. |
| Exploit ScenarioDerived | An unauthenticated attacker targets an APISIX gateway (3.17.0-3.18.0) that fronts applications using the saml-auth plugin for SSO. Because the plugin does not properly verify the SAML assertion's cryptographic signature, the attacker forges or tampers with a SAML response to assert any identity and is granted an authenticated session for that user on every protected route, gaining the victim's access to upstream applications. No public exploit code was provided, and exploitation requires no authentication and no user interaction per the description. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Signature verification failure in the Apache APISIX saml-auth plugin (versions 3.17.0 through 3.18.0) allows an attacker to forge SAML assertions and impersonate arbitrary users on every route protected by that plugin, and the plugin's DEFAULT configuration is vulnerable, so no additional misconfiguration or attacker-controlled precondition is needed. The vendor's CVSS 4.0 vector scores the issue 6.4 with PR:L and no direct CIA impact on the vulnerable component (only SC:H/SI:H on subsequent systems), which understates the practical effect described by the vendor itself as 'any unauthenticated attacker could impersonate any user'; our independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N, and the PR:N versus PR:L discrepancy between the description and the vendor vector should be verified. No public exploit code and no confirmed active exploitation were identified at time of analysis; exposure is limited to the two-release version window and to deployments that actually enable saml-auth on at least one route.
RemediationAI
The primary fix is to upgrade Apache APISIX to 3.19.0 or later, which the vendor states resolves the issue (Vendor-released patch: 3.19.0), as documented in the Apache advisory at https://lists.apache.org/thread.html/1230fnojnmc7bfz3n0nkt7tkcld9d1sc. If an immediate upgrade is not possible, the most effective compensating control is to remove or disable the saml-auth plugin from all route configurations (or, at minimum, take saml-auth-protected routes out of service) so that no route relies on the unverified assertion path, accepting the trade-off that SAML single sign-on for those routes stops working and users must fall back to another authentication mechanism such as key-auth, JWT with a trusted issuer, or OIDC; a second option is to terminate SAML validation in front of APISIX (for example at a reverse proxy or identity-aware proxy that performs strict signature verification on the assertion and only forwards already-authenticated traffic), with the trade-off of added architectural complexity and a second component that must itself be kept patched. Restricting network access to saml-auth-protected endpoints to known identity-provider source addresses reduces the attacker pool but does not fix the underlying verification flaw and can break legitimate federated or mobile clients, so it should be treated as a stopgap only. Note that the plugin is vulnerable in its default configuration, so tuning plugin options is not a substitute for upgrading.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache APISIX is an OpenResty/NGINX-based API gateway whose behavior is extended by Lua plugins attached per route, and the affected component is the saml-auth authentication plugin that consumes SAML responses/assertions from an identity provider to establish a session before proxying traffic. The vulnerability class is CWE-347, Improper Verification of Cryptographic Signature: the plugin fails to correctly validate the cryptographic signature protecting the SAML assertion, so an attacker can present a forged or modified assertion that the gateway treats as authentic and then inherit whatever identity that assertion names. The supplied CPE entry (cpe:2.3:a:apache_software_foundation:apache_apisix:*:*:*:*:*:*:*:*) is version-agnostic, so the concrete affected range comes from the vendor description (3.17.0 through 3.18.0). Because signature validation is the single trust anchor for the whole SSO flow, a defect here collapses authentication to attacker-controlled input; the accompanying reference tags ('Jwt Attack', 'Information Disclosure') indicate the same signature-verification weakness has been characterized in token/signature terms, consistent with the broader pattern of trusting unverified tokens or assertions rather than binding a validated signature to the exact assertion being consumed.
Know when Apache Apisix gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
Description says unauthenticated (PR:N) network impersonation of any user; gateway compromise crosses scope (S:C) to grant high confidentiality/integrity access on protected upstreams, no availability impact.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
DescriptionCVE.org
Improper verification of cryptographic signature vulnerability in Apache APISIX.
Any unauthenticated attacker could impersonate any user on every route protected by the saml-auth plugin under default configuration. This issue affects Apache APISIX: from 3.17.0 through 3.18.0.
Users are recommended to upgrade to version 3.19.0, which fixes the issue.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Apache Apisix
View allHeader injection in Apache APISIX 2.12.0 through 3.15.0 lets remote attackers smuggle attacker-controlled HTTP headers t
Unauthenticated remote denial of service in Apache APISIX 1.3.0 through 3.18.0 allows an attacker to exhaust gateway wor
Sensitive authentication tokens in Apache APISIX OpenID Connect plugin transmit in cleartext when connecting to identity
Authentication bypass in Apache APISIX versions 2.2 through 3.16.0 allows remote attackers to circumvent authentication
HMAC authentication replay in Apache APISIX 3.11.0 through 3.16.0 permits remote attackers who have captured a valid hma
Authentication bypass in Apache APISIX's jwe-decrypt plugin (versions 3.8.0 through 3.16.0) allows unauthenticated netwo
Apache APISIX versions 2.14.1 through 3.18.0 can serve requests to protected upstream endpoints without authentication w
Identity header spoofing in Apache APISIX versions 2.12.0 through 3.16.0 allows a low-privileged network attacker to man
Authentication bypass in Apache APISIX 3.0.0 through 3.16.0 allows a network-accessible attacker holding valid credentia
Incorrect authorization in the Apache APISIX authz-casdoor plugin allows a network-authenticated attacker to cross-authe
Identity header spoofing in Apache APISIX's openid-connect plugin (versions 2.3 through 3.16.0) enables low-privileged n
Apache APISIX 2.99.0 through 3.15.0 transmits sensitive log data in cleartext over HTTP when exporting logs to Tencent C
EUVD-2026-90765
GHSA-9cp4-6jfv-7725
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB