Quick answers
- Is CVE-2026-45746 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45746 being exploited in the wild.
- How severe is CVE-2026-45746?
- Critical severity, with a CVSS score of 9, published 5 June 2026.
- Which products and versions are affected?
- Termix-SSH Termix < 2.3.2.
- Is there a fix for CVE-2026-45746?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45746 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-45746?
- Check whether you run Termix-SSH Termix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A broken access control vulnerability (CWE-639) exists in the Termix File Manager due to improper validation of the 'sessionId' parameter. The backend fails to verify that the client-provided sessionId belongs to the currently authenticated user, trusting the user-controlled identifier instead. Because these session IDs are predictable numeric values, an authenticated attacker can iterate through IDs to hijack active SSH connections. This grants the attacker access to various file operations (read, write, upload) and the 'executeFile' endpoint, effectively resulting in Remote Code Execution (RCE) on the remote VPS instances managed by other users. The issue is addressed in version 2.3.2.
Affected products
- Termix-SSH Termix < 2.3.2
Timeline
- 2026-05-31: advisory: Initial GitHub security advisory published
- 2026-06-05: disclosed: CVE published to NVD dataset