Skip to main content
Menu
CVEs

mcp-ssh-manager command injection in SSH database helper functions

Affects mcp-ssh-manager's ssh_db_list, ssh_db_dump and ssh_db_import tools, which interpolate their arguments into shell commands. Fixed in 3.6.7.

CVE-2026-77383Published , updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.6.7
Who is exposed
Specific setups only

Summary

A command injection flaw in bvisible's mcp-ssh-manager lets an attacker with low-privilege login send shell metacharacters through its database helper functions over the network, running arbitrary commands on the configured SSH target. The commands run as the account the MCP server uses on that target, and no user action is needed.

Written by a model

Original description

mcp-ssh-manager is an MCP server for managing servers over SSH with human approval, an encrypted vault, and a live audit trail. Prior to 3.6.7, ssh_db_list, ssh_db_dump, ssh_db_import, and ssh_db_restore in src/database-manager.js interpolate caller-controlled database, table, collection, file path, user, host, port, and password values into shell-evaluated command strings without neutralization. Shell metacharacters in these arguments therefore execute arbitrary commands on the configured SSH target as the account used by the MCP server. ssh_db_list is classified as read-only and remains available in readonly and restricted server security modes, so this path bypasses the command-execution boundary those modes are intended to enforce. The dump and import builders are blocked in readonly mode but remain vulnerable in the default unrestricted mode. The earlier version 3.6.5 hardening covered only ssh_db_query query text; it did not protect the list, dump, import, or restore builders, or the connection flags used by query builders. This issue is fixed in version 3.6.7.

Who should check

Teams running bvisible mcp-ssh-manager 3.6.6 or earlier with the ssh_db_* database tools exposed to callers

Not fixed by: Readonly and restricted modes do not contain a caller that can reach ssh_db_list.

“A caller able to invoke a database tool with a crafted value”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Uses the ssh_db_* database tools (ssh_db_list, ssh_db_dump, ssh_db_import), whose arguments are interpolated into shell commands ssh_db_list remains available in readonly and restricted per-server security modes ssh_db_dump and ssh_db_import are injectable in the default unrestricted mode
  2. Upgrade to a fixed version: 3.6.7.

  3. Workaround: Avoid exposing the ssh_db_* tools by disabling the database tool group

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77383 (mcp-ssh-manager: Command injection in mcp-ssh-manager database helpers (ssh_db_list / ssh_db_dump / ssh_db_import)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77383 (entry last updated 2026-11-20):
Affected:
- bvisible mcp-ssh-manager: fixed in 3.6.7
Fixed versions: 3.6.7.
Conditions (all must be true for the bug to be hit):
- Uses the ssh_db_* database tools (ssh_db_list, ssh_db_dump, ssh_db_import), whose arguments are interpolated into shell commands (source: https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-4jx9-2fwj-pg4j)
- ssh_db_list remains available in readonly and restricted per-server security modes (source: https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-4jx9-2fwj-pg4j)
- ssh_db_dump and ssh_db_import are injectable in the default unrestricted mode (source: https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-4jx9-2fwj-pg4j)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Avoid exposing the ssh_db_* tools by disabling the database tool group (source: https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-4jx9-2fwj-pg4j)
CISA KEV: CVE-2026-77383 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77383 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-4jx9-2fwj-pg4j
- https://github.com/bvisible/mcp-ssh-manager/pull/51
- https://github.com/bvisible/mcp-ssh-manager/commit/4c19b350f36f5f09f15662f8d19d2ba9cdf38bd0
- https://github.com/bvisible/mcp-ssh-manager/releases/tag/v3.6.7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77383
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77383"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · bvisible/mcp-ssh-manager · Advisory GHSA-4jx9-2fwj-pg4j
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-77383
Other links 3
RepositoryGitHub · bvisible/mcp-ssh-manager · Pull request #51
RepositoryGitHub · bvisible/mcp-ssh-manager · Commit 4c19b350
RepositoryGitHub · bvisible/mcp-ssh-manager · Release v3.6.7

Questions about CVE-2026-77383

Is CVE-2026-77383 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The ssh_db_* database tools place their arguments directly into shell commands without sanitizing them. This lets the arguments run arbitrary commands on the configured SSH target, under the account the MCP server uses.

Source: github.com

Which versions are affected by CVE-2026-77383?

mcp-ssh-manager: before 3.6.7.

Source: cve.now feed data

Am I affected, and how do I check?

Versions of mcp-ssh-manager before 3.6.7 are in the affected range. ssh_db_dump and ssh_db_import are injectable in the default unrestricted mode, and ssh_db_list also remains available in the readonly and restricted per-server security modes. Check the installed mcp-ssh-manager version and whether the database tool group is enabled.

Source: github.com

How do I fix CVE-2026-77383?

Upgrade mcp-ssh-manager to 3.6.7. Until then, avoid exposing the ssh_db_* tools by disabling the database tool group.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.