mcp-ssh-manager: shell injection in the ssh_db_* and ssh_backup_* tools ran commands on managed servers, even through 'read-only' tools allowed in readonly mode (CVE-2026-77383, CVE-2026-129995; fixed 3.8.5)
mcp-ssh-manager (npm) is an MCP server that lets AI agents manage servers over SSH with approvals, a vault and readonly/restricted security modes. Its database tools (ssh_db_list, ssh_db_dump, ssh_db_import, ssh_db_restore) and backup tools (ssh_backup_create, ssh_backup_list, ssh_backup_restore, ssh_backup_schedule) pasted tool arguments such as database, table, paths, user, host and password into shell command strings without escaping. A crafted argument from a malicious or compromised MCP client, or from an agent steered by prompt injection, ran arbitrary commands on the managed server as the configured SSH user. ssh_db_list and ssh_backup_list are treated as read-only and stayed available in readonly and restricted modes, so those modes did not stop it; ssh_backup_schedule could persist commands through cron. Fixed in 3.6.7 (database tools) and 3.8.5 (backup tools).
What it is
CVE-2026-77383 (GHSA-4jx9-2fwj-pg4j): src/database-manager.js interpolated caller-controlled values into shell-evaluated commands. The earlier 3.6.5 fix only covered ssh_db_query's query text. Fixed in 3.6.7 with a central shellQuote() across all database builders.
CVE-2026-129995 (GHSA-qwwm-vrm9-4mw8): the same class of bug in src/backup-manager.js and inline backup handlers in src/index.js, which the 3.6.7 fix did not cover. ssh_backup_list skipped the server policy check. Fixed in 3.8.5.
Affected: mcp-ssh-manager <= 3.6.6 (database tools) and <= 3.8.4 (backup tools). 3.6.7 was released on 11 July 2026 and 3.8.5 on 28 August 2026; NVD published both CVEs on 20 November 2026.
How to check
- Run npm ls -g mcp-ssh-manager (or check your MCP client config for the version pinned with npx).
- If you relied on readonly or restricted mode to limit what an agent can do on your servers, treat versions below 3.8.5 as offering no command-execution boundary.
How to fix
- Upgrade mcp-ssh-manager to 3.8.5 or later.
- Review cron entries and backup schedules on managed servers for jobs you didn't create.
- Use a dedicated low-privilege SSH account for the MCP server rather than root or an admin user.
npm ls -g mcp-ssh-manager
# on each managed server, look for unexpected scheduled jobs
crontab -l Sources
- criticalMalicious npm package @guicai777/mcp-doctor posed as an MCP diagnostic tool and dropped a hidden Windows executable, with a README telling users to run mshta (MAL-2026-20295)
- criticalCVE-2026-77359: Jupyter MCP Server's /api/connect and /api/stop routes skipped the token and Origin checks, so a website or network caller could repoint it to an attacker's Jupyter backend (fixed 1.0.3)
- criticalMalicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp
- criticalCVE-2026-76807: Doist's official Todoist MCP HTTP server let any website use DNS rebinding to read, create and delete your Todoist data (fixed 10.3.3)