Command InjectionWeakness · CWE-77

CVE-2026-42453

HIGH · 8.7 CVSS v4.0 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges 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.1.0, the extractArchive and compressFiles endpoints in file-manager.ts use double-quoted strings for shell command construction, unlike all other file manager operations which use single-quote escaping. Double quotes allow $(command) substitution, enabling command injection on the remote SSH host. This issue has been patched in version 2.1.0.

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 extractArchive and compressFiles endpoints in Termix file-manager.ts use double-quoted strings for shell command construction instead of the single-quote escaping used by other file manager operations. Double quotes enable $(command) substitution, allowing authenticated users to inject arbitrary commands that execute on the remote SSH host.

MitigationUpgrade to Termix version 2.1.0 or later, which replaces double-quote with single-quote escaping in the affected endpoints.

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

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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
    Locate the Termix application or its package.json/binary and retrieve the version number (e.g., via 'termix --version', checking package.json, or reviewing the application metadata)
    Affected if The version is before 2.1.0 (e.g., 2.0.x, 1.x.x, or unversioned)
  2. Locate the file-manager.ts source file
    Find the file-manager.ts file in the Termix installation directory or source code repository and examine its contents
    Affected if The file exists and contains extractArchive and/or compressFiles function implementations
  3. Inspect shell command construction in extractArchive
    Search the file-manager.ts file for the extractArchive function and examine how it builds shell commands - look for whether it uses double quotes (\") or single quotes (') around variables
    Affected if The code uses double-quoted strings (e.g., \"${variable}\") when passing user-controlled input to shell commands
  4. Inspect shell command construction in compressFiles
    Search the file-manager.ts file for the compressFiles function and examine how it builds shell commands - look for whether it uses double quotes (\") or single quotes (') around variables
    Affected if The code uses double-quoted strings (e.g., \"${variable}\") when passing user-controlled input to shell commands
  5. Verify archive features are accessible
    Check if the file manager's archive extraction and compression endpoints are exposed and enabled in the running Termix service configuration
    Affected if The extractArchive or compressFiles endpoints are accessible to authenticated users without additional network restrictions

If Termix version is before 2.1.0 AND the file-manager.ts uses double-quoted shell command construction in extractArchive or compressFiles, the environment is vulnerable to command injection via the archive features.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Termix version 2.1.0 or later, which replaces double-quote with single-quote escaping in the affected endpoints.

Recommended fix Moderate confidence

2.1.0

  1. Upgrade Termix to version 2.1.0 or later to remediate the command injection vulnerability in the extractArchive and compressFiles endpoints.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-42453 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