Skip to main content
VulnerabilityPublished Updated

CVE-2026-53542: Termix · OS Command Injection

Affects TermixSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2.3.2 soon.

Data as of 16 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 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 16 Nov 2026.

What to do

Upgrade Termix and termix-ssh/Termix to 2.3.2.

Affected software

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

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.3.2 or later, where this vulnerability has been fixed by properly handling file basenames passed to the tar command. No other mitigation is required as the fix is official and addresses the root cause.

Description

CVE-2026-53542 is an OS command injection vulnerability in Termix-SSH's Termix platform prior to version 2.3.2. The flaw exists in the archive creation endpoint where file basenames are passed to the tar command without proper sanitization or an end-of-options marker. This allows an attacker with SSH file-manager access to craft filenames that are interpreted as tar options, leading to arbitrary command execution with the privileges of the SSH user. The vulnerability is fixed in version 2.3.2.

References

Community reviews

Loading reviews…