# CVE-2026-133116: Termix 1.7.0 before 26.11.2 Path Traversal via Username in Database Export


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-2h7w-g8jj-275r, GHSA-w3fm-vvr2-7vg3

## What is CVE-2026-133116?

CVE-2026-133116 is a medium-severity vulnerability in Termix-SSH Termix, published on 19 Nov 2026. 

### Official description

Termix 1.7.0 before 26.11.2 contains a path traversal vulnerability that allows authenticated users to write files outside the export directory via crafted usernames. Attackers can self-register with a username containing ../ segments and request POST /database/export to plant attacker-controlled SQLite files in writable directories, enabling disk exhaustion.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

1 open source package ship an affected version, including termix-ssh/termix.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `termix-ssh/termix` | GitHub | `pkg:github/termix-ssh/termix` | From 1.7.0 | 26.11.2 |

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

Upgrade termix-ssh/termix to 26.11.2 or later.

## Is CVE-2026-133116 being exploited?

There is no known exploitation of CVE-2026-133116 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133116 is a medium-severity vulnerability in Termix-SSH Termix, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133116 in the wild and no public exploit code.

Affected packages and fixed versions:
- termix-ssh/termix (GitHub): affected from 1.7.0; fixed in 26.11.2

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-133116/ (Markdown: https://insights.sbomify.com/CVE-2026-133116/index.md)
```

## Sources

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

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