Quick answers
- Is CVE-2026-45749 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45749 being exploited in the wild.
- How severe is CVE-2026-45749?
- High severity, with a CVSS score of 8.1, published 5 June 2026.
- Which products and versions are affected?
- Termix-SSH Termix <= 2.1.0.
- Is there a fix for CVE-2026-45749?
- A patch was published on 2026-06-04: Version 2.3.2 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45749 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-45749?
- Check whether you run Termix-SSH Termix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability in the `POST /users/totp/disable` and `POST /users/totp/backup-codes` endpoints of Termix (prior to version 2.3.2) allows for the bypass of multi-factor authentication (MFA) requirements. The root cause is an improper authentication logic in `src/backend/database/routes/users.ts` that uses an 'OR' instead of an 'AND' condition when verifying credentials; providing a valid password allows the code to skip TOTP verification entirely. An attacker with a valid session and the user's password can disable MFA or generate new backup codes, effectively downgrading the account to single-factor authentication. This issue is resolved in version 2.3.2.
Affected products
- Termix-SSH Termix <= 2.1.0
Timeline
- 2026-05-31: advisory: GHSA-wqfw-rqj7-fv9m published
- 2026-06-04: patched: Version 2.3.2 released
- 2026-06-05: disclosed: CVE-2026-45749 published