What is the CVSS score of CVE-2026-45745?

CVE-2026-45745 has a CVSS 3.1 base score of 8.0 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of Termix Desktop are affected by CVE-2026-45745?

Termix Desktop versions 1.7.0 and later disable TLS certificate validation, enabling network-positioned attackers to intercept HTTPS connections and steal user credentials and session tokens.

How to fix or mitigate CVE-2026-45745?

Within 24 hours: Restrict Termix Desktop 1.7.0+ to trusted networks only; for essential use, require all traffic through a corporate VPN with certificate pinning. Within 7 days: Contact Termix vendor for patch availability and timeline; audit credential/token access logs from users running affected versions. Within 30 days: Migrate users to a patched Termix Desktop release (once available) or transition to an alternative tool with proper TLS validation.

Termix Desktop CVE-2026-45745

EUVD-2026-34871 HIGH

Improper Certificate Validation (CWE-295)

2026-06-05 GitHub_M

Information Disclosure Termix Termix Ssh

8.0

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.0 HIGH

AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 18:41 vuln.today

DescriptionGitHub Advisory

Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. Starting in version 1.7.0, Termix Desktop (Electron) disables TLS certificate validation, allowing a machine-in-the-middle attacker to intercept and modify HTTPS traffic to the configured Termix server. This can lead to credential theft and JWT/session theft during login and normal use. As of time of publication, no known patched versions are available.

AnalysisAI

Machine-in-the-middle interception of HTTPS traffic in Termix Desktop (Electron) starting at version 1.7.0 allows attackers positioned on the network path to steal login credentials and JWT/session tokens because the Electron client disables TLS certificate validation entirely. No public exploit identified at time of analysis and the issue is not in CISA KEV, but the CVSS 8.0 rating with scope-change and the absence of any vendor-released patch make this a meaningful concern for any user running Termix Desktop on untrusted networks.

Technical ContextAI

Termix is a web-based server management platform that bundles an SSH terminal, tunneling and file editor; the desktop distribution is built on Electron, which uses Chromium's network stack for outbound HTTPS calls to the user-configured Termix server. The root cause is CWE-295 (Improper Certificate Validation): the Electron client appears to override the default certificate verification routine (typically by setting rejectUnauthorized: false, handling the certificate-error event to always call event.preventDefault(), or accepting any peer in app.on('select-client-certificate')), so any TLS certificate - including self-signed or attacker-controlled - is accepted as valid. The affected CPE is cpe:2.3:a:termix-ssh:termix:*:*:*:*:*:*:*:* covering all versions from 1.7.0 onward of the Termix-SSH/Termix project.

RemediationAI

No vendor-released patch identified at time of analysis, so users should monitor https://github.com/Termix-SSH/Termix/security/advisories/GHSA-r9gw-3w87-mhh7 and upgrade as soon as a fixed release is published. In the interim, the most effective compensating control is to stop using Termix Desktop on untrusted networks and instead access the Termix server via the browser-based web UI from a trusted endpoint, where the browser's standard certificate validation applies; alternatively, tunnel all client-to-server traffic through a trusted VPN or SSH port-forward so MITM positions are removed even if TLS validation is broken (side effect: added latency and operational complexity). Operators should also rotate any JWTs/session tokens and user passwords that may have transited untrusted networks since first using Termix Desktop ≥1.7.0, and consider pinning the Termix server to a private network segment until a fix ships.