Skip to content

CVE-2025-49596: Anthropic MCP Inspector 0.0.0.0-Day Remote Code Execution

Density:
HERMES

HERMES THREAT SCORE & AGENTIC SUPPLY CHAIN RISK

Target: Anthropic Model Context Protocol Inspector (@modelcontextprotocol/inspector antรฉrieures ร  0.14.1)
Confidence: 98%
92 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 18 / 20
Weaponization 19 / 20
Exposure 18 / 20
Prevalence 18 / 20
Impact 20 / 20
Exploit Maturity 18 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

While standard NVD feeds assign CVSS 9.4 with a requirement for user interaction (UI:R), Hermes rates CVE-2025-49596 at an HTS of 92 with an EXTREME Agentic Security Score (HASS 93). Because developers routinely run the MCP Inspector while browsing technical forums, documentation, and web resources, binding unauthenticated stdio execution to 0.0.0.0 enables 1-click compromise of the developer's workstation, local cloud credentials, and connected AI agent tools.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2025-49596: Anthropic MCP Inspector 0.0.0.0-Day Remote Code ExecutionVULNERABILITY

Connected Nodes: 2
Active Relationships (Outgoing)
→ exploitsAGENTIC ATTACK_PATTERNAAP-004: Semantic Tool Poisoning
92% VERY_HIGH

Attacker registers rogue MCP tools or skills with weaponized docstrings and deceptive metadata that trick the model into routing sensitive user tasks to attacker-controlled functions.

๐Ÿ” Why is this related? (Evidence & Provenance)

“CVE-2025-49596 weaponizes the agentic attack pattern formalized under AAP-004.”

Supporting Verified Evidence:
→ exploitsAGENTIC ATTACK_PATTERNAAP-003: Tool Parameter Tampering & Built-in Bypass
92% VERY_HIGH

Adversarial subversion of structured tool execution arguments (SQL, Shell, Filepath) passed from an LLM agent to host OS tools or MCP endpoints.

๐Ÿ” Why is this related? (Evidence & Provenance)

“CVE-2025-49596 weaponizes the agentic attack pattern formalized under AAP-003.”

Supporting Verified Evidence:
ParameterTechnical SpecificationOperational Impact
CVE IdentifierCVE-2025-49596Official MITRE / NVD entry
Associated CWEsCWE-306: Missing Authentication
CWE-94: Code Injection
Unrestricted developer proxy command execution
CVSS v3.1 Score9.4 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Hermes Threat Score (HTS)92 / 100 (CRITICAL)High exploitation feasibility against AI developers
Hermes Agentic Score (HASS)93 / 100 (EXTREME)Direct compromise of autonomous tool calling runtime
Affected Package@modelcontextprotocol/inspectorVersions antรฉrieures ร  0.14.1
Fixed Version0.14.1Binds to localhost, enforces bearer tokens & Origin checks
Ecosystem & ProtocolModel Context Protocol (MCP)Core debugging and testing utility

The Model Context Protocol (MCP) Inspector is designed to let AI developers test and debug MCP servers interacting with models such as Claude Desktop, Cursor, and custom agent swarms.

graph LR
AttackerSite["Malicious Webpage (Drive-By)"] -->|Fetch / Proxy Command| LocalProxy["0.0.0.0:6277 (MCP Inspector)"]
LocalProxy -->|stdio Spawn| HostShell["Developer Host Shell (zsh / bash)"]
HostShell -->|Compromise| Secrets["AWS / GitHub / Vault Credentials"]

When launched via npx @modelcontextprotocol/inspector, earlier versions initialized an Express/WebSocket proxy bound to 0.0.0.0:6277:

  1. Lack of Origin Validation: The proxy server did not inspect the HTTP Origin or Host headers on incoming requests.
  2. Missing Transport Authentication: No API key, session cookie, or ephemeral token was required to invoke the proxy API.
  3. Arbitrary Stdio Command Invocation: The proxy exposes endpoints allowing the client to specify which binary to run and which arguments to pass to spawn an MCP server. A malicious website visited in any tab could issue a simple cross-origin fetch (fetch('http://localhost:6277/api/...') or http://0.0.0.0:6277) instructing the proxy to spawn a reverse shell or download malware.

  • Process Trees: Look for @modelcontextprotocol/inspector or node processes spawning child shells (sh, bash, powershell.exe, curl, wget) that do not match expected MCP server development paths.
  • Port Binding: Listening sockets on 0.0.0.0:6277 rather than 127.0.0.1:6277.
  • Browser History & Logs: Outbound cross-origin network requests directed towards port 6277 originating from untrusted public web origins.
rule Detect_MCP_Inspector_RCE_Exploitation {
meta:
description = "Detects HTTP payloads attempting to exploit CVE-2025-49596 via MCP Inspector proxy"
author = "Hermes Codex Epistemic Research"
cve = "CVE-2025-49596"
reference = "https://hermes-codex.net/cve/2025/cve-2025-49596/"
strings:
$p1 = "6277" ascii
$p2 = "modelcontextprotocol" ascii nocase
$p3 = "stdio" ascii
$c1 = "command" ascii
$c2 = "args" ascii
$c3 = "/bin/sh" ascii
$c4 = "powershell" ascii nocase
condition:
all of ($p*) and 2 of ($c*)
}

Update @modelcontextprotocol/inspector to version 0.14.1 or later:

Terminal window
npm install -g @modelcontextprotocol/inspector@latest
# Or force npx to fetch the patched release
npx @modelcontextprotocol/inspector@latest