# CVE-2026-45746: Termix Vulnerable to Arbitrary Command Execution via Session Hijacking

> Attackers can hijack File Manager sessions to execute arbitrary commands on other users' remote servers due to improper session validation.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-cx2r-843c-vww8

## What is CVE-2026-45746?

CVE-2026-45746 is a critical missing authorization vulnerability in Termix-SSH Termix, published on 5 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. Prior to version 2.3.2, the File Manager functionality in Termix contains a critical Broken Access Control vulnerability due to improper validation of the sessionId parameter. The backend trusts a client-controlled identifier without verifying that it belongs to the authenticated user. This allows an attacker to manipulate the value and access active File Manager sessions belonging to other users. Since these sessions are tied to SSH connections to remote VPS instances, exploitation allows unauthorized interaction with another user's remote filesystem. Because the File Manager exposes functionality such as file reading, writing, uploading, and execution, this vulnerability enables direct command execution on another user's VPS (RCE). Version 2.3.2 patches the issue.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-45746?

It affects 1 product.


Products: Termix Termix.

## How do I fix CVE-2026-45746?

No fix has been published for CVE-2026-45746 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45746 being exploited?

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

Public exploit code:

- CVE-2026-45746, CVE-2026-45750, CVE-2026-53547 — three critical vulnerabilities in Termix: cross-tenant session hijacking, OS command injection, and account takeover (github_poc): https://github.com/GabrielHA12/Termix-research

## Other vulnerabilities in Termix-SSH Termix

- [CVE-2026-45744](https://insights.sbomify.com/CVE-2026-45744/): Termix has an OS Command Injection in File Manager resolvePath endpoint (critical 9.9)
- [CVE-2026-45748](https://insights.sbomify.com/CVE-2026-45748/): Termix Vulnerable to Remote Code Execution via SSH Tunnel Forward Command Injection (critical 9.8)
- [CVE-2025-59951](https://insights.sbomify.com/CVE-2025-59951/): Termix' official Docker image contains an authentication bypass vulnerability (critical 9.2)
- [CVE-2026-45750](https://insights.sbomify.com/CVE-2026-45750/): Termix Vulnerable to Arbitrary Command Execution in File Manager (critical 9.0)
- [CVE-2026-45743](https://insights.sbomify.com/CVE-2026-45743/): Termix has a File-Manager Session Hijack via Missing Ownership Check (IDOR) (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45746 is a critical missing authorization vulnerability in Termix-SSH Termix, published on 5 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45746 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-45746/ (Markdown: https://insights.sbomify.com/CVE-2026-45746/index.md)
```

## Sources

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

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