Critical RCE in Anthropic MCP Inspector (CVE-2025-49596) Enables Browser-Based Exploits | Oligo Security
Source Reddit NetSec
Not known to be exploited · public detection template (Nuclei) · 44% EPSS · CVSS 9.4 Critical : upgrade to 0.14.1 as a priority.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 44.4% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.14.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Jun 2025
Detectable: evidence found.
nuclei template: MCP Inspector < 0.14.0 UnauthenticatedRemote Code Execution
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade modelcontextprotocol/inspector to 0.14.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmodelcontextprotocol/inspectorpkg:github/modelcontextprotocol/inspectorOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Given the absence of an official patch, European organizations should implement several specific mitigations: 1) Restrict access to the MCP Inspector interface to trusted networks and authenticated users only, ideally behind VPNs or zero-trust network architectures. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious input patterns or exploit attempts targeting the MCP Inspector. 3) Monitor network and application logs for unusual activity, especially unexpected code execution attempts or anomalous browser requests. 4) Conduct internal audits to identify all instances of MCP Inspector deployment and isolate or disable non-essential instances until patched. 5) Educate users about phishing and social engineering risks that could deliver browser-based exploits. 6) Engage with Anthropic or vendors for timely updates and apply patches immediately upon release. 7) Use endpoint detection and response (EDR) tools to detect post-exploitation behaviors. 8) Consider deploying browser isolation technologies to reduce exposure to drive-by attacks. These targeted actions go beyond generic advice by focusing on access control, monitoring, and containment specific to the MCP Inspector context.
Description
Critical RCE in Anthropic MCP Inspector (CVE-2025-49596) Enables Browser-Based Exploits | Oligo Security Source: https://www.oligo.security/blog/critical-rce-vulnerability-in-anthropic-mcp-inspector-cve-2025-49596