# CVE-2025-59951: Termix' official Docker image contains an authentication bypass vulnerability

> Attackers can bypass authentication to access stored SSH credentials in Termix Docker deployments using Nginx reverse proxies.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2025
- **Updated:** 6 Oct 2025
- **Also known as:** GHSA-92cw-877q-6r94

## What is CVE-2025-59951?

CVE-2025-59951 is a critical authentication bypass vulnerability in LukeGus Termix, published on 1 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. The official Docker image  for Termix versions 1.5.0 and below, due to being configured with an Nginx reverse proxy, causes the backend to retrieve the proxy's IP instead of the client's IP when using the req.ip method. This results in isLocalhost always returning True. Consequently, the /ssh/db/host/internal endpoint can be accessed directly without login or authentication. This endpoint records the system's stored SSH host information, including addresses, usernames, and passwords, posing an extremely high security risk. Users who use the official Termix docker image, build their own image using the official dockerfile, or utilize reverse proxy functionality will be affected by this vulnerability. This issue is fixed in version 1.6.0.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity), CWE-348 (Use of Less Trusted Source), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-59951?

It affects 1 product.


Products: Termix Termix.

## How do I fix CVE-2025-59951?

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

## Is CVE-2025-59951 being exploited?

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

## Other vulnerabilities in LukeGus 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-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)
- [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-2025-59951 and fix it if it is affected.

What it is: CVE-2025-59951 is a critical authentication bypass vulnerability in LukeGus Termix, published on 1 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59951 exists.

Affected product: LukeGus 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-2025-59951/ (Markdown: https://insights.sbomify.com/CVE-2025-59951/index.md)
```

## Sources

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

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