Critical mcp-remote Vulnerability Enables Remote Code Execution, Impacting 437,000+ Downloads
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2025-49596 | Unauthenticated RCE in Anthropic MCP Inspector (versions below 0.14.1) CVE-2025-49596 is a missing-authentication flaw (CWE-306) in the MCP Inspector, a developer tool for testing and debugging Model Context Protocol (MCP) servers: the Inspector's proxy component accepts unauthenticated requests from the client, which allows unauthenticated requests to launch MCP commands over stdio. An attacker who can reach the proxy while a developer is running the Inspector (CVSS 4.0 indicates network attack vector with user interaction required, consistent with a malicious page or request reaching the developer's machine) can trigger these command launches without any credentials. Successful exploitation yields remote code execution on the developer's machine with the privileges of the Inspector process, which is why the flaw is rated 9.4 (critical) on the CVSS 4.0 scale with high impact across confidentiality, integrity, and availability. Affected users are developers running any MCP Inspector version below 0.14.1 on their workstations; this is a developer-tool flaw, not a production-server flaw, so only machines actively running the tool are exposed at any given time. No public proof-of-concept or confirmed in-the-wild exploitation is currently known and the issue is not yet in CISA's KEV catalog, but EPSS assigns a 42.7% probability of exploitation within 30 days (99th percentile), indicating high near-term risk. Do: Upgrade MCP Inspector to version 0.14.1 or later immediately on all developer machines. Until upgraded, do not keep the Inspector or its proxy component running while browsing untrusted websites or handling untrusted content, and shut it down when not actively debugging. Audit developer workstations and CI images for running or installed Inspector instances and verify the installed version is 0.14.1 or later. | 9.4 | 43% |
| largeon the order of hundreds of thousands of developer installations (peer MCP ecosystem tooling shows 437k+ downloads) | ||
| CVE-2025-53109 +1 in the same advisory: …53110 | Model Context Protocol Servers is a collection of reference implementations for the model context protocol (MCP). Model Context Protocol Servers is a collection of reference implementations for the model context protocol (MCP). Versions of Filesystem prior to 0.6.4 or 2025.7.01 could allow access to unintended files via symlinks within allowed directories. Users are advised to upgrade to 0.6.4 or 2025.7.01 resolve. NVD description · AI analysis pending | 7.3 | <1% | — | — | ||
| CVE-2025-6514 | Critical OS Command Injection in mcp-remote Enables RCE via Untrusted MCP Servers CVE-2025-6514 is a critical OS command injection vulnerability (CWE-78, CVSS 9.6) in the mcp-remote tool, which bridges remote MCP (Model Context Protocol) servers into AI clients. It is triggered when mcp-remote connects to a malicious or untrusted MCP server: crafted data in the authorization_endpoint response URL supplied during the OAuth flow is executed as an operating system command. An attacker who controls or compromises an MCP server gains remote code execution on the host running mcp-remote with that user's privileges, potentially exposing enterprise secrets such as API keys, tokens, and local files. Affected users are developers and organizations running mcp-remote to connect AI agents and MCP clients to third-party MCP servers; the data does not specify affected version ranges. As of now there is no public proof-of-concept and it is not in CISA KEV, but the 77.9% EPSS score (100th percentile) indicates a very high probability of exploitation within 30 days. Do: Upgrade mcp-remote to the latest patched release per the JFrog/vendor advisory (exact fixed version is not specified in this data). Until patched, avoid pointing mcp-remote at untrusted or third-party MCP servers, and audit existing MCP server configurations for servers you do not control. Because the flaw executes commands during the authorization flow, also check hosts that ran mcp-remote for signs of unexpected command execution. | 9.6 | 78% |
| large≈437,000+ downloads of the mcp-remote npm package |
Full article879 words · extracted from thehackernews.com · click to collapse
Cybersecurity researchers have discovered a critical vulnerability in the open-source mcp-remote project that could result in the execution of arbitrary operating system (OS) commands.
The vulnerability, tracked as CVE-2025-6514, carries a CVSS score of 9.6 out of 10.0.
"The vulnerability allows attackers to trigger arbitrary OS command execution on the machine running mcp-remote when it initiates a connection to an untrusted MCP server, posing a significant risk to users – a full system compromise," Or Peles, JFrog Vulnerability Research Team Leader, said.
Mcp-remote is a tool that sprang forth following Anthropic's release of Model Context Protocol (MCP), an open-source framework that standardizes the way large language model (LLM) applications integrate and share data with external data sources and services.
It acts as a local proxy, enabling MCP clients like Claude Desktop to communicate with remote MCP servers, as opposed to running them locally on the same machine as the LLM application. The npm package has been downloaded more than 437,000 times to date.
The vulnerability affects mcp-remote versions from 0.0.5 to 0.1.15. It has been addressed in version 0.1.16 released on June 17, 2025. Anyone using mcp-remote that connects to an untrusted or insecure MCP server using an affected version is at risk.
"While previously published research has demonstrated risks from MCP clients connecting to malicious MCP servers, this is the first time that full remote code execution is achieved in a real-world scenario on the client operating system when connecting to an untrusted remote MCP server," Peles said.
The shortcoming has to do with how a malicious MCP server operated by a threat actor could embed a command during the initial communication establishment and authorization phase, which, when processed by mcp-remote, causes it to be executed on the underlying operating system.
While the issue leads to arbitrary OS command execution on Windows with full parameter control, it results in the execution of arbitrary executables with limited parameter control on macOS and Linux systems.
To mitigate the risk posed by the flaw, users are advised to update the library to the latest version and only connect to trusted MCP servers over HTTPS.
"While remote MCP servers are highly effective tools for expanding AI capabilities in managed environments, facilitating rapid iteration of code, and helping ensure more reliable delivery of software, MCP users need to be mindful of only connecting to trusted MCP servers using secure connection methods such as HTTPS," Peles said.
"Otherwise, vulnerabilities like CVE-2025-6514 are likely to hijack MCP clients in the ever-growing MCP ecosystem."
The disclosure comes after Oligo Security detailed a critical vulnerability in the MCP Inspector tool (CVE-2025-49596, CVSS score: 9.4) that could pave the way for remote code execution.
Tenable, which also discovered and reported CVE-2025-49596, said the flaw has to do with the fact that the interactive web user interface (UI) launched by MCP Inspector via localhost to communicate with servers lacks any authentication out-of-the-box.
This enables an attacker on the same network as the proxy instance to inject malicious commands into it, a scenario called NeighborJacking, or trick a victim into visiting a malicious web page, which embeds JavaScript code that can deceive the proxy component into executing arbitrary code through a cross-site attack.
The vulnerabilities lay bare the hidden risks lurking in what has been described as an "USB-C" or a universal adapter for AI application, becoming the backbone infrastructure for connecting apps to different data and tools.
"It's crucial to enforce security fundamentals in server development and tool usage," security researcher Rémy Marot said. "Adhering to basic security practices can significantly mitigate risks from vulnerabilities in novel systems and prevent devastating attacks."
Earlier this month, two other high-severity security defects were uncovered in Anthropic's Filesystem MCP Server, which, if successfully exploited, could let attackers break out of the server's sandbox, manipulate any file on the host, and achieve code execution.
The two flaws, per Cymulate, are listed below -
- CVE-2025-53110 (CVSS score: 7.3) - A directory containment bypass that makes it possible to access, read, or write outside of the approved directory (e.g., "/private/tmp/allowed_dir") by using the allowed directory prefix on other directories (e.g., "/private/tmp/allow_dir_sensitive_credentials"), thereby opening the door data theft and possible privilege escalation
- CVE-2025-53109 (CVSS score: 8.4) - A symbolic link (aka symlink) bypass stemming from poor error handling that can be used to point to any file on the file system from within the allowed directory, allowing an attacker to read or alter critical files (e.g., "/etc/sudoers") or drop malicious code, resulting in code execution by making use of Launch Agents, cron jobs, or other persistence techniques
Both shortcomings impact all Filesystem MCP Server versions prior to 0.6.3 and 2025.7.1, which include the relevant fixes.
"This vulnerability is a serious breach of the Filesystem MCP Servers security model," security researcher Elad Beber said about CVE-2025-53110. "Attackers can gain unauthorized access by listing, reading or writing to directories outside the allowed scope, potentially exposing sensitive files like credentials or configurations."
"Worse, in setups where the server runs as a privileged user, this flaw could lead to privilege escalation, allowing attackers to manipulate critical system files and gain deeper control over the host system."
Found this article interesting? Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post.
Text extracted automatically; images, tables and formatting may be missing. Original: https://thehackernews.com/2025/07/critical-mcp-remote-vulnerability.html