dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-42454

CRITICAL · 9.9 CVSS v3.1 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 →
100/100
Remediation priority · Urgent
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.1.0, all Docker container management endpoints in Termix interpolate the containerId URL path parameter and WebSocket message field directly into shell commands executed via ssh2.Client.exec() on remote managed servers without any sanitization or validation. An authenticated attacker can inject arbitrary OS commands by crafting a malicious container ID, achieving Remote Code Execution on any managed server. 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

Termix versions prior to 2.1.0 contain a command injection vulnerability in Docker container management endpoints where the containerId parameter from both URL paths and WebSocket messages is directly interpolated into shell commands executed via ssh2.Client.exec() without sanitization or validation, allowing authenticated attackers to execute arbitrary OS commands on managed servers.

MitigationUpgrade to Termix version 2.1.0 or later, which includes proper input sanitization for container IDs. If immediate patching is not possible, implement validation whitelists for container identifiers and avoid direct string interpolation in shell command execution.

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
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 Termix installation and version
    Check for Termix installation by looking for the binary or service. Common locations: /opt/termix, /usr/local/bin/termix, or as a system service. Run 'termix --version' or check the package manager. Compare the version number to 2.1.0.
    Affected if Termix is installed and the version is below 2.1.0
  2. Confirm Docker management feature is enabled
    Inspect Termix configuration files (typically in /etc/termix/ or ~/.termix/) for Docker-related settings. Look for 'docker', 'container', or 'docker management' enabled flags in configuration files like config.yaml or settings.json.
    Affected if Docker container management endpoints are enabled in Termix configuration
  3. Verify remote SSH access is configured
    Check if Termix is configured to manage remote servers via SSH. Look for SSH connection profiles, remote host configurations, or ssh2.Client settings in the Termix configuration directory.
    Affected if Termix has SSH-based remote server management configured and enabled
  4. Audit container command execution logs
    Review Termix application logs, system logs, or Docker daemon logs for unusual container commands. Look for container IDs that contain shell metacharacters (like ;, |, $, `, or &&) in the command history or access logs.
    Affected if Logs show container commands with unexpected characters or patterns indicating injection attempts

The environment is affected if Termix version is below 2.1.0 AND Docker container management is enabled with SSH-based remote execution capabilities.

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 includes proper input sanitization for container IDs. If immediate patching is not possible, implement validation whitelists for container identifiers and avoid direct string interpolation in shell command execution.

Recommended fix High confidence

Termix version 2.1.0

  1. Upgrade Termix to version 2.1.0 or later
  2. Verify the upgrade was successful by checking the Termix version
  3. Test Docker container management functionality to ensure the fix works and legitimate operations still function

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42454 — 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-42454 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