dbcve.org
TermixApplication

CVE-2026-45744

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 2.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. Prior to version 2.3.2, the GET /ssh/file_manager/ssh/resolvePath endpoint in Termix is vulnerable to OS command injection. The endpoint uses double-quote escaping for shell command construction, which does not prevent $(...) and backtick command substitution. Any authenticated user with an active File Manager SSH session can execute arbitrary commands on the connected remote host. Version 2.3.2 patches the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Termix server management platform prior to version 2.3.2 contains an OS command injection vulnerability in the GET /ssh/file_manager/ssh/resolvePath endpoint. The endpoint uses double-quote escaping when constructing shell commands for path resolution, but this escaping fails to prevent command substitution via $(...) and backticks. Any authenticated user with an active File Manager SSH session can execute arbitrary commands on the connected remote host.

MitigationUpgrade to Termix version 2.3.2 or later to obtain the patched version. If immediate upgrading is not feasible, restrict access to the File Manager functionality to trusted users only until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TermixApplication
Affected:>= 2.1.0, < 2.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Termix version
    Check the Termix application version through its built-in about panel, package manager, or by querying the application binary with 'termix --version' or 'termix -v'
    Affected if Version is 2.1.0 through 2.3.1 (inclusive) - meaning >= 2.1.0 and < 2.3.2
  2. Verify File Manager SSH module is accessible
    Log into Termix and navigate to the File Manager section, then confirm the SSH connection feature is available/enabled in the user interface
    Affected if File Manager SSH functionality is present and accessible to the authenticated user account
  3. Check for active or recent SSH sessions
    Review Termix session logs, active connection list, or configuration files in the Termix data directory for any established SSH connections via File Manager
    Affected if Any active or recent SSH sessions exist in the File Manager module

If Termix version is 2.1.0 through 2.3.1 AND the File Manager SSH feature is accessible with active or historical sessions, the environment is vulnerable to command injection via the /ssh/file_manager/ssh/resolvePath endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.2 or later
Fixed in 2.3.2
Interim mitigation

Upgrade to Termix version 2.3.2 or later to obtain the patched version. If immediate upgrading is not feasible, restrict access to the File Manager functionality to trusted users only until the patch can be applied.

Recommended fix High confidence

2.3.2

  1. 1. Back up your current Termix installation and configuration data
  2. 2. Download Termix version 2.3.2 from the official GitHub repository or release channel
  3. 3. Stop the running Termix service
  4. 4. Install version 2.3.2 following standard upgrade procedures
  5. 5. Verify the installation completed successfully
  6. 6. Restart the Termix service
  7. 7. Test that the /ssh/file_manager/ssh/resolvePath endpoint is properly sanitizing input and no longer vulnerable to command injection

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Termix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45744 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data