A relative path traversal vulnerability in Apache APISIX allows callers of the MCP endpoint to invoke endpoints that were never declared in the OpenAPI document, bypassing intended access controls.
Quick Take
- What: CVE-2026-124726, a path traversal flaw in Apache APISIX MCP endpoint that allows unauthorized endpoint access
- Who is affected: Apache APISIX version 3.19.0 deployments using MCP endpoints
- CVSS score: 6.9 (Medium severity)
- Fixed version: Apache APISIX 3.20.0
- What to do: Upgrade to version 3.20.0 immediately
In plain English
Apache APISIX is a gateway that controls access to web services. It has a feature called MCP (Model Context Protocol) that is supposed to only allow access to specific endpoints listed in an OpenAPI document. A bug was found where an attacker could trick the MCP endpoint into calling other endpoints that were not supposed to be accessible, using the same credentials. This only affects version 3.19.0.
What you should do: If you run Apache APISIX 3.19.0, you should upgrade to 3.20.0. If you don’t use Apache APISIX or use a different version, you can ignore this.
What happened
The vulnerability exists in Apache APISIX version 3.19.0. An attacker calling the MCP endpoint can exploit a relative path traversal flaw to invoke endpoints that the OpenAPI document never declared. The attack works under the declared tool’s HTTP method and uses the credentials that the Route adds.
The Apache Software Foundation assigned this vulnerability CVE-2026-124726 and rated it with a CVSS score of 6.9 (Medium severity). The issue represents an unintended proxy vulnerability combined with path traversal.
What you should do
Users running Apache APISIX 3.19.0 should upgrade to version 3.20.0, which fixes the issue. The Apache Software Foundation recommends this upgrade for all affected users.
What it means
This vulnerability undermines the access control model of Apache APISIX’s MCP endpoint feature. Organizations relying on OpenAPI document declarations to restrict which endpoints can be accessed through MCP may have exposed additional endpoints unintentionally. The flaw could allow attackers to access internal APIs or services that should have been protected, potentially leading to unauthorized data access or operations.
The vulnerability affects only a single version (3.19.0), suggesting it was introduced in that release and quickly identified and patched.



