A security report has tightened the nerves within the AI development community.
On April 15, the cybersecurity company OX Security released a report revealing a design flaw in Anthropic's MCP (Model Context Protocol), which could lead to remote code execution and affect more than 200,000 AI servers.
MCP is an open-source standard launched by Anthropic in November 2024, aimed at enabling AI large models to seamlessly connect and operate various external data and tools. It is currently widely used by developers to build AI applications.

The root of the problem lies in the STDIO interface of the MCP SDK. This interface was originally designed to start local server processes, but the underlying execution logic has serious vulnerabilities—it runs any incoming operating system commands, even if the server fails to start, the command is still executed without any verification or warning. OX Security clearly pointed out that this is not a low-level coding mistake, but a design decision at the architectural level.
The vulnerability affects a wide range, covering all 11 programming languages officially supported by Anthropic, including Python, TypeScript, Java, Go, Rust, and other mainstream languages. Any developer building on MCP automatically inherits this risk.
OX Security spent months testing four types of attacks in real environments. LangFlow has 915 public instances, and attackers can obtain session tokens and take full control without needing an account; Letta AI was attacked via a man-in-the-middle attack, allowing researchers to execute arbitrary commands directly on production servers; Flowise's whitelist filtering protection was easily bypassed; the most severe was the Windsurf IDE vulnerability, where users only need to visit a malicious website, without any clicks, attackers can execute arbitrary commands locally. This vulnerability has been assigned a CVE number.
After receiving the vulnerability notification on January 7 this year, Anthropic responded by stating it was "expected behavior," and nine days later, they only updated a security document, advising developers to use the STDIO adapter cautiously, without making any architectural changes.
Researchers also uploaded malicious servers to 11 major MCP markets for testing, and 9 of them were directly accepted without any security review, with only GitHub's hosted registry intercepting the submission.
