mcp-ssh-tool has file transfer path policy bypass and bearer token comparison hardening
GHSA-j7h9-2jh7-g967 · published 2026-05-07 · updated 2026-08-16
- Severity
- High
- CVSS score
- 8.7
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.1.1
Affected versions may allow policy bypass in transfer path handling under specific configurations, and may expose a timing side channel in bearer-token comparison for HTTP deployments.
Upgrade mcp-ssh-tool to 2.1.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.
Upgrade to mcp-ssh-tool >= 2.1.1.
For deployments that cannot immediately upgrade: avoid exposing HTTP transport beyond loopback use strict filesystem policy configuration avoid granting MCP clients access to sensitive local transfer paths monitor audit logs for unexpected transfer operations
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mcp-ssh-tool | npm | <= 2.1.0 | 2.1.1 |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
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.