CVE-2026-79763: Termix · Use of Single-factor Authentication
Affects TermixSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.5.1 when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 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 8 Nov 2026.
What to do
Upgrade Termix and termix-ssh/Termix to 2.5.1.
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-SSH to version 2.5.1 or later, where this vulnerability is fixed. No other mitigation is required as the fix restores proper two-factor authentication enforcement on the affected endpoints.
Description
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 2.4.0 until 2.5.1, the POST /users/totp/disable and POST /users/totp/backup-codes endpoints accept the account password as the sole reauthentication factor after a 2.4.0 refactor regressed the two-factor check introduced for CVE-2026-45749. In src/backend/database/routes/user-totp-routes.ts, verifyTotpReauth returns success when bcrypt.compare validates the password, while each endpoint chooses password or totp_code as an interchangeable credential. An attacker who has a victim's authenticated session and knows the password can disable TOTP or regenerate and invalidate backup codes without an authenticator or valid second factor, weakening the account to single-factor authentication. This issue is fixed in version 2.5.1.
References
- github.com/Termix-SSH/Termix/security/advisories/GHSA-x9h9-f7jc-8jwj (opens in a new tab)
- github.com/Termix-SSH/Termix/pull/1067 (opens in a new tab)
- github.com/Termix-SSH/Termix/commit/22124e1bc49c8cedad57b31de9c51ad39f3d4432 (opens in a new tab)
- github.com/Termix-SSH/Termix/commit/ddbdd5c437c2296607dfaa4265d6f63fbc1ca92e (opens in a new tab)
- github.com/Termix-SSH/Termix/releases/tag/release-2.5.1-tag (opens in a new tab)