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

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-vx59-rf9w-9jv8

## 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 (Missing Critical Step in Authentication)

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

## Is CVE-2026-42452 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42452 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42452 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42452 exists.

Affected product: Termix-SSH Termix. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42452/ (Markdown: https://insights.sbomify.com/CVE-2026-42452/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42452
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42452
- OSV: https://osv.dev/vulnerability/CVE-2026-42452

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42452/
Summaries are generated and may contain mistakes; the official description above is the record.