CVE-2025-59951: LukeGus Termix · Use of Less Trusted Source
Affects LukeGus TermixSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical : upgrade to 1.6.0 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 4.5% chance of exploitation in 30 days – higher than 91% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.6.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade LukeGus Termix to 1.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LukeGus Termix | Affected
| Fixed in
|
AI-suggested
1. Upgrade Termix installations to version 1.6.0 or later immediately to apply the official fix addressing the IP detection and authentication bypass. 2. Review and harden reverse proxy configurations, ensuring that the backend correctly identifies client IP addresses, for example by properly setting and validating X-Forwarded-For headers. 3. Implement network segmentation and access controls to restrict access to Termix management interfaces only to trusted internal networks or VPNs. 4. Enable logging and monitoring on Termix endpoints, especially /ssh/db/host/internal, to detect any unauthorized access attempts. 5. Avoid using the official Docker image without customization; consider building images with enhanced security configurations and minimal privileges. 6. Conduct regular audits of stored SSH credentials and rotate passwords or keys if exposure is suspected. 7. Employ multi-factor authentication and additional layers of access control around server management tools. 8. Educate DevOps and security teams about the risks of relying on less trusted sources for client identification in proxy environments.
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.