CVE-2026-124726: Path traversal in Apache APISIX MCP endpoint bypasses OpenAPI restrictions

A path traversal vulnerability in Apache APISIX versions 3.19.0 allows attackers to invoke endpoints not declared in OpenAPI documents through the MCP endpoint, using credentials added by the Route.

Christopher Ort
By Christopher Ort · 2 min read
Share
A network gateway server rack with warning lights illuminated in a data center
Image: AI-generated, i10X
On this page
  1. Quick Take
  2. In plain English
  3. What happened
  4. What you should do
  5. What it means
  6. Sources

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.

i10X Quick Take

Quick Take

  1. What: CVE-2026-124726, a path traversal flaw in Apache APISIX MCP endpoint that allows unauthorized endpoint access
  2. Who is affected: Apache APISIX version 3.19.0 deployments using MCP endpoints
  3. CVSS score: 6.9 (Medium severity)
  4. Fixed version: Apache APISIX 3.20.0
  5. 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.

Sources

Christopher Ort

Christopher Ort

Christopher Ort handles SEO, AI agent workflows and PR & partnerships at i10x.ai, the all-in-one AI workspace built by i10X Global Pte. Ltd. in Singapore. He is a graduate of Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU). He is the author of “The Style Penalty”, a study published on SSRN that analyses 1,576 evaluation decisions by four frontier AI models to show how AI-written CVs fare in automated hiring screens; the research has been covered by heise online and t3n.

Editor's picks

  1. GAO Report: ChatGPT, Claude, Gemini and Grok Produced Viable Attack Plans After Safeguards Were Bypassed
  2. ResolveAI SRE-1: A 27B Model Trained to Find the Root Cause of Production Incidents
  3. Reson8 Rumble-2-Flash: Open-Weight 0.5B Speech Recognition Model Covers 40+ Languages
  4. Pika Enact Lets Creators Direct AI Video Actors and Cameras in Real Time
  5. Google Stitch Loop: An Always-On Product Agent That Fixes Security, Speed and Accessibility via Pull Requests