Termix: Missing authorization in SSH host credential resolution exposes stored credentials

published 2026-08-19 2 mo ago modified 2026-09-09 1 mo ago also EUVD-2026-62859

cvss: 9.6; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits: 0; none known

Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. Prior to 2.3.2, the terminal WebSocket accepts a user-controlled hostConfig.id and src/backend/ssh/host-resolver.ts resolves that host without requiring ownership or explicit access. When no credential is shared with the requester, resolveHostById performs an owner credential fallback, and src/backend/ssh/terminal.ts combines that credential with attacker-controlled ip, port, and username values. An authenticated low-privileged user can therefore make Termix authenticate to an attacker-controlled SSH server and disclose another user's stored SSH password or private-key material while the victim user's data key is unlocked. This issue is fixed in version 2.3.2.

Patch / fix

links 3

github.com/Termix-SSH/Termix@52f4e51 commit
github.com/Termix-SSH/Termix#874 pull request
github.com/Termix-SSH/Termix/releases/tag/release-2.3.2-tag release

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: total
Assessed: 2 mo ago (2026-08-20)

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/Termix-SSH/Termix/security/advisories/GHSA-57gp-39c7-4g9r referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.6	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Affected products

Termix-SSH Termix

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key
CWE-862 Missing Authorization

References

Sources

CVE List CVE-2026-53546
NVD CVE-2026-53546

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary