Skip to main content
VulnerabilityPublished

CVE-2026-77383: bvisible mcp-ssh-manager · OS Command Injection

Affects bvisible mcp-ssh-managerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 3.6.7 soon.

Data as of 20 Nov 2026, 18:44 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.7
Patch
Available – fixed in 3.6.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade bvisible mcp-ssh-manager to 3.6.7.

Affected software

ProductAffectedFixed in
bvisiblemcp-ssh-managerAffected
  • <3.6.7
Fixed in
  • 3.6.7

AI-suggested

Upgrade mcp-ssh-manager to version 3.6.7 or later, where this vulnerability is fixed. Prior versions are vulnerable and should not be used in production environments. No other mitigations are indicated or effective given the nature of the injection flaw.

Description

CVE-2026-77383 is a high-severity OS command injection vulnerability in bvisible mcp-ssh-manager versions prior to 3.6.7. Several functions in the database manager module improperly interpolate user-controlled inputs into shell commands without sanitization, allowing arbitrary command execution on SSH targets. The ssh_db_list function remains exploitable even in readonly and restricted modes, bypassing intended security boundaries. This issue was fixed in version 3.6.7.

References

Community reviews

Loading reviews…