Vulnerability · Published May 8, 2026 · Assigned by GitHub_M

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

High 8.1

In plain English

A high-severity security flaw in Termix from Termix-SSH. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 24% of all known vulnerabilities).

Severity (CVSS 3.1)8.1High

Exploit odds (30 days)0.3%top 76.4% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

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.

Affected products (as reported)

Vendor	Product	Versions
Termix-SSH	Termix	< 2.1.0

Weakness: CWE-304 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

References

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