Skip to main content
VulnerabilityPublished Updated

CVE-2026-42454: Termix · OS Command Injection

Affects TermixSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 2.1.0 as a priority.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 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 29 Oct 2026.

What to do

Upgrade Termix and termix-ssh/Termix to 2.1.0.

Affected software

ProductAffectedFixed in
Termix-SSHTermixAffected
  • <2.1.0
Fixed in
  • 2.1.0
GitHubtermix-ssh/Termixpkg:github/termix-ssh/TermixOther threatsAffected
  • <2.1.0
Fixed in
  • 2.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Termix to version 2.1.0 or later, where this vulnerability has been patched. No other mitigation or temporary workaround is documented. Since this is not a cloud service, remediation depends on applying the official fix.

Description

Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. Prior to version 2.1.0, all Docker container management endpoints in Termix interpolate the containerId URL path parameter and WebSocket message field directly into shell commands executed via ssh2.Client.exec() on remote managed servers without any sanitization or validation. An authenticated attacker can inject arbitrary OS commands by crafting a malicious container ID, achieving Remote Code Execution on any managed server. This issue has been patched in version 2.1.0.

References

Community reviews

Loading reviews…