GHSA-j7h9-2jh7-g967 — mcp-ssh-tool
GHSA-j7h9-2jh7-g967 is a security vulnerability in mcp-ssh-tool. A fix is available for mcp-ssh-tool — see the affected versions and patch details below.
mcp-ssh-tool has file transfer path policy bypass and bearer token comparison hardening
Real-World Exposure
mcp-ssh-toolReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Summary
mcp-ssh-tool has released version 2.1.1 with security hardening for transfer path authorization and HTTP bearer authentication.
The release addresses:
- insufficient local path policy enforcement in transfer-related filesystem handling
- incomplete canonicalization and segment-boundary handling for deny-prefix path policy checks
- non-constant-time HTTP bearer token comparison
Impact
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.
Patched Version
Upgrade to mcp-ssh-tool >= 2.1.1.
npm install -g mcp-ssh-tool@latest
Workarounds
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
Credits
Reported by dodge1218.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | mcp-ssh-tool | all versions | 2.1.1npm install mcp-ssh-tool@2.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mcp-ssh-tool, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mcp-ssh-tool to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j7h9-2jh7-g967 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j7h9-2jh7-g967 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-j7h9-2jh7-g967. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j7h9-2jh7-g967 in your dependencies?
O3 Security finds GHSA-j7h9-2jh7-g967 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.