# CVE-2026-22804: Cross-site scripting in Termix

> Attackers can execute arbitrary JavaScript via unsanitized SVG files in the File Manager, leading to session hijacking or local file inclusion.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jan 2026
- **Updated:** 13 Jan 2026
- **Also known as:** GHSA-m3cv-5hgp-hv35

## What is CVE-2026-22804?

CVE-2026-22804 is a high-severity cross-site scripting vulnerability in Termix-SSH Termix, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, 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. From 1.7.0 to 1.9.0, Stored Cross-Site Scripting (XSS) vulnerability exists in the Termix File Manager component. The application fails to sanitize SVG file content before rendering it. This allows an attacker who has compromised a managed SSH server to plant a malicious file, which, when previewed by the Termix user, executes arbitrary JavaScript in the context of the application. The vulnerability is located in src/ui/desktop/apps/file-manager/components/FileViewer.tsx. This vulnerability is fixed in 1.10.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Termix Termix.

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

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

## Is CVE-2026-22804 being exploited?

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

Public exploit code:

- This repository contains a Proof of Concept (PoC) exploit for the Stored Cross-Site Scripting (XSS) vulnerability in Termix, which can lead to Local File Inclusion (LFI) in the Electron environment and Session Hijacking. (github_poc): https://github.com/ThemeHackers/CVE-2026-22804

## 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-45746](https://insights.sbomify.com/CVE-2026-45746/): Termix Vulnerable to Arbitrary Command Execution via Session Hijacking (critical 9.0)
- [CVE-2026-45750](https://insights.sbomify.com/CVE-2026-45750/): Termix Vulnerable to Arbitrary Command Execution in File Manager (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22804 is a high-severity cross-site scripting vulnerability in Termix-SSH Termix, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, 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-22804 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-22804/ (Markdown: https://insights.sbomify.com/CVE-2026-22804/index.md)
```

## Sources

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

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