How severe is GHSA-j7h9-2jh7-g967?

No CVSS score has been assigned to GHSA-j7h9-2jh7-g967 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j7h9-2jh7-g967?

GHSA-j7h9-2jh7-g967 affects the following packages: mcp-ssh-tool (npm). Ecosystems affected: npm.

How do I fix GHSA-j7h9-2jh7-g967?

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.

How do I detect GHSA-j7h9-2jh7-g967 in my npm dependencies?

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.

How do I mitigate GHSA-j7h9-2jh7-g967 if there is no patch (or I can't update yet)?

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.

Is GHSA-j7h9-2jh7-g967 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j7h9-2jh7-g967 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-j7h9-2jh7-g967 published, and has it been updated?

GHSA-j7h9-2jh7-g967 was published on May 7, 2026 and was last updated on May 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

mcp-ssh-tool has file transfer path policy bypass and bearer token comparison hardeningGHSA-j7h9-2jh7-g967

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.

Published

May 7, 2026

Updated

May 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 21, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

mcp-ssh-toolnpm

0downloads / week

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mcp-ssh-tool`	all versions	2.1.1`npm install mcp-ssh-tool@2.1.1`

Detection & mitigation playbook

Open-source dependency

Detect
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.

Frequently Asked Questions

## 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. ## P

O3 Security · Impact-Aware SCA

Is GHSA-j7h9-2jh7-g967 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

mcp-ssh-tool has file transfer path policy bypass and bearer token comparison hardeningGHSA-j7h9-2jh7-g967

Real-World Exposure

Description

Summary

Impact

Patched Version

Workarounds

Credits

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-j7h9-2jh7-g967 in your dependencies?