CVE-2026-79761: Termix SSH key deployment command injection

CVE-2026-79761 · Severity: medium · CVSS 6.6 · Published 2026-09-24

Termix is a web-based platform for managing SSH connections, terminals, and file transfers to remote servers. An authenticated user can deploy a malicious SSH credential that executes arbitrary commands on a target server with the privileges of the SSH account being configured. This allows an attacker with Termix access to take over remote systems or access sensitive data.

Technologies: Termix-SSH Termix. Vendors: Termix-SSH.

Quick answers

Is CVE-2026-79761 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-79761 being exploited in the wild.
How severe is CVE-2026-79761?
Medium severity, with a CVSS score of 6.6, published 24 September 2026.
Which products and versions are affected?
Termix-SSH Termix 1.7.0 to 2.5.0.
Is there a fix for CVE-2026-79761?
A patch was published on 2026-07-19: Version 2.5.1 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-79761 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-79761?
Check whether you run Termix-SSH Termix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the SSH key deployment flow (src/backend/database/routes/credential-deploy-routes.ts) where a user-controlled public-key token is used to derive a grep pattern that is interpolated into double-quoted shell commands executed on the target host. The grep -F verification paths do not properly escape command substitution or shell metacharacters, allowing authenticated users to break out of the grep context and execute arbitrary commands with the target account's privileges.

Affected products

  • Termix-SSH Termix 1.7.0 to 2.5.0

Timeline

  • 2026-09-24: disclosed
  • 2026-07-19: patched: Version 2.5.1 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.