CVE-2026-42452 Termix: Pending-TOTP temporary token can regenerate backup codes and neutralize TOTP
Attackers can bypass TOTP two-factor authentication by using a temporary login token on regular endpoints, leading to account takeover.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-42452?
CVE-2026-42452 is a high-severity authentication bypass vulnerability in Termix-SSH Termix, published on 8 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. Prior to version 2.1.0, /users/login issues a temporary JWT (temp_token) for TOTP-enabled accounts. That token carries a pendingTOTP state and should only be valid for the second-factor flow. However, the auth middleware accepts this token on regular authenticated endpoints. This effectively turns 2FA into single-factor (password) for impacted accounts. This issue has been patched in version 2.1.0.
Weakness: CWE-304
Which versions are affected by CVE-2026-42452?
How do I fix CVE-2026-42452?
No fix has been published for CVE-2026-42452 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-42452 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42452 exists.
Sources
Also known as GHSA-vx59-rf9w-9jv8.