CVE-2026-53546: Termix · Insecure Direct Object Reference
Affects TermixSource CVE Database V5
Not known to be exploited · CVSS 9.6 Critical : upgrade to 2.3.2 as a priority.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% 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:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Termix-SSHTermix | Affected
| Fixed in
|
GitHubtermix-ssh/Termixpkg:github/termix-ssh/TermixOther threats | Affected
| Fixed in
|
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 authorization bypass vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Patch status is confirmed as an official fix in version 2.3.2.
Description
CVE-2026-53546 is a critical authorization bypass vulnerability in Termix, a web-based server management platform. Versions prior to 2.3.2 allow an authenticated low-privileged user to exploit a flaw in the terminal WebSocket host resolution process. The vulnerability arises because the system accepts a user-controlled hostConfig.id and resolves it without verifying ownership or explicit access. This can lead to Termix authenticating to an attacker-controlled SSH server and disclosing another user's stored SSH credentials while their data key is unlocked. The issue is fixed in Termix version 2.3.2.
References
- github.com/Termix-SSH/Termix/security/advisories/GHSA-57gp-39c7-4g9r (opens in a new tab)
- github.com/Termix-SSH/Termix/pull/874 (opens in a new tab)
- github.com/Termix-SSH/Termix/commit/52f4e51ae03b5b8d2608e1383e2ccf79d290132b (opens in a new tab)
- github.com/Termix-SSH/Termix/releases/tag/release-2.3.2-tag (opens in a new tab)