CVE-2026-94220 in APISIX
Summary
by MITRE • 10/01/2026
Cross-Site request forgery (CSRF) vulnerability in feishu-auth and dingtalk-auth plugins in Apache APISIX.
An attacker who can get a user to click a crafted link may cause that user's browser session on a protected route to be established under the attacker's identity instead of their own. Any work the user then performs in that session, including uploads, form submissions, and account bindings, lands in the attacker's account. 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.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 10/01/2026
The vulnerability identified in Apache APISIX versions ranging from 3.17.0 through 3.18.0 represents a critical Cross-Site Request Forgery (CSRF) flaw within the feishu-auth and dingtalk-auth plugins. This security defect allows an attacker to exploit the trust that these authentication modules place in user browsers, enabling unauthorized actions to be performed on behalf of authenticated users without their knowledge or consent. The core issue stems from insufficient validation mechanisms when processing state-changing requests initiated by third-party sites, which is a classic manifestation of CSRF where the application fails to distinguish between legitimate user-initiated requests and maliciously crafted ones originating from external domains.
From a technical perspective, the vulnerability affects the integration points for Feishu and DingTalk authentication flows. When an authenticated user visits a webpage controlled by an attacker, that page can contain hidden forms or script-based mechanisms designed to submit specific HTTP requests to Apache APISIX endpoints associated with these plugins. Because modern browsers automatically include session cookies and other credentials in such cross-origin requests if the target domain matches the cookie's scope, the server processes these requests as valid actions performed by the logged-in user. This bypasses standard authentication checks because the browser handles credential transmission transparently, leaving the backend application vulnerable to state-changing operations that should require explicit user intent verification.
The operational impact of this vulnerability is severe and multifaceted. An attacker who successfully lures a victim into clicking a crafted link or loading a malicious page can force the victim's session on protected routes to be established under the attacker's identity rather than their own. This effectively allows for account takeover scenarios where subsequent actions taken by the user, such as file uploads, form submissions, and critical configuration changes like binding accounts to external services, are attributed to the attacker’s account. Consequently, sensitive data can be exfiltrated, system configurations can be altered maliciously, or further phishing campaigns can be launched using the compromised identity, leading to significant reputational damage and potential regulatory non-compliance depending on the nature of the processed data.
This vulnerability aligns with CWE-352, which defines Cross-Site Request Forgery as a weakness where a web application executes unwanted state-changing requests from users who have been authenticated. In terms of offensive security frameworks, this attack vector corresponds to techniques found in MITRE ATT&CK under Tactic TA0001 Initial Access and specifically relates to methods that exploit trust relationships between browsers and servers, often categorized under social engineering or browser-based attacks depending on the delivery mechanism used by the adversary. The lack of anti-CSRF tokens or strict origin validation for these specific plugin endpoints creates a gap in defense-in-depth strategies typically expected from API gateways handling sensitive authentication workflows.
To mitigate this risk immediately, organizations running affected versions must upgrade Apache APISIX to version 3.19.0 or later, where the issue has been resolved by implementing robust CSRF protection mechanisms such as synchronized token patterns and stricter origin header validation for state-changing requests within the feishu-auth and dingtalk-auth modules. In addition to upgrading, administrators should ensure that their deployment configurations enforce strict Content Security Policy headers and utilize SameSite cookie attributes set to Strict or Lax where applicable to further reduce the attack surface. Continuous monitoring of authentication logs for anomalous patterns can also aid in detecting potential exploitation attempts while patching efforts are underway.