MCP Inspector proxy server lacks authentication between the Inspector client and proxy
CVE-2025-49596 · GHSA-7f8r-222p-6f5g · published 2025-06-13 · updated 2025-07-09
- Severity
- Critical
- CVSS score
- 9.4
- Chance of exploitation (EPSS)
- 39.9%
- Fixed in
- 0.14.1
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
Versions of MCP Inspector below 0.14.1 are vulnerable to remote code execution due to lack of authentication between the Inspector client and proxy, allowing unauthenticated requests to launch MCP commands over stdio. Users should immediately upgrade to version 0.14.1 or later to address these vulnerabilities.
Upgrade @modelcontextprotocol/inspector to 0.14.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @modelcontextprotocol/inspector | npm | < 0.14.1 | 0.14.1 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- HighMCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server@modelcontextprotocol/inspector
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.