Summary
mcp-ssh-tool has file transfer path policy bypass and bearer token comparison hardening
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
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.
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.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-J7H9-2JH7-G967? GHSA-J7H9-2JH7-G967 is a high-severity path traversal vulnerability in mcp-ssh-tool (npm), affecting versions <= 2.1.0. It is fixed in 2.1.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of mcp-ssh-tool are affected by GHSA-J7H9-2JH7-G967? mcp-ssh-tool (npm) versions <= 2.1.0 is affected.
- Is there a fix for GHSA-J7H9-2JH7-G967? Yes. GHSA-J7H9-2JH7-G967 is fixed in 2.1.1. Upgrade to this version or later.
- Is GHSA-J7H9-2JH7-G967 exploitable, and should I be worried? Whether GHSA-J7H9-2JH7-G967 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-J7H9-2JH7-G967 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-J7H9-2JH7-G967? Upgrade
mcp-ssh-toolto 2.1.1 or later.