CVE-2026-42452
- Source
- https://cve.org/CVERecord?id=CVE-2026-42452
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-42452.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-42452
- Aliases
-
- GHSA-vx59-rf9w-9jv8
- Published
- 2026-05-08T22:54:12Z
- Modified
- 2026-10-28T02:30:40Z
- Severity
-
- 8.1 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N CVSS Calculator
- Summary
- Termix: Pending-TOTP temporary token can regenerate backup codes and neutralize TOTP
- Details
-
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.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-304" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/42xxx/CVE-2026-42452.json" }- References
Affected packages
Git / github.com/termix-ssh/termix
Affected ranges
- Type
- GIT
- Repo
- https://github.com/termix-ssh/termix
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
-
Show details
{ "extracted_events": [ { "range": [ { "introduced": "0" }, { "fixed": "2.1.0" } ], "source": "AFFECTED_FIELD", "strategy": "StringRangeExpression" }, { "original_tag": "release-2.1.0-tag", "range": [ { "fixed": "c67d914e61ef9fc6e97347337ea59ffa9196d560" } ], "source": "REFERENCES_TAG" }, { "range": [ { "introduced": "0" }, { "fixed": "2.1.0" } ], "source": "DESCRIPTION" } ] }