CVE-2025-66401: kapilduraphe mcp-watch · OS Command Injection
Affects kapilduraphe mcp-watchSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubkapilduraphe/mcp-watchpkg:github/kapilduraphe/mcp-watchOther 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
1. Immediate upgrade: Organizations should upgrade mcp-watch to a version beyond 0.1.2 once a patched release is available. 2. Input validation and sanitization: Until a patch is released, implement strict validation on the githubUrl input to reject any shell metacharacters or unexpected input patterns. 3. Execution environment hardening: Run mcp-watch with the least privileges possible, ideally within a sandboxed or containerized environment to limit the impact of any successful exploitation. 4. Disable or restrict execSync usage: If feasible, modify the source code to avoid using execSync with unsanitized inputs or replace it with safer alternatives that do not invoke a shell. 5. Network controls: Restrict network access to the mcp-watch service to trusted IPs and monitor network traffic for anomalous command execution attempts. 6. Monitoring and detection: Deploy host-based intrusion detection systems (HIDS) and log monitoring to detect suspicious command executions or unexpected process spawning. 7. Incident response readiness: Prepare incident response plans specific to command injection attacks, including forensic analysis and containment procedures. 8. Vendor engagement: Engage with the vendor kapilduraphe for updates, patches, and guidance on secure configurations.
Description
MCP Watch is a comprehensive security scanner for Model Context Protocol (MCP) servers. In 0.1.2 and earlier, the MCPScanner class contains a critical Command Injection vulnerability in the cloneRepo method. The application passes the user-supplied githubUrl argument directly to a system shell via execSync without sanitization. This allows an attacker to execute arbitrary commands on the host machine by appending shell metacharacters to the URL.