CVE-2026-42454
Remote Code Execution in Termix via Container ID Injection
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| termix | termix | to 2.1.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Termix, a web-based server management platform. Before version 2.1.0, Termix's Docker container management endpoints directly insert the containerId parameter from the URL path and WebSocket messages into shell commands executed on remote servers without any sanitization or validation.
Because of this lack of input validation, an authenticated attacker can craft a malicious container ID that injects arbitrary operating system commands. This leads to Remote Code Execution (RCE) on any managed server.
The issue was fixed in Termix version 2.1.0.
How can this vulnerability impact me? :
This vulnerability can have severe impacts because it allows an authenticated attacker to execute arbitrary commands on any managed server remotely.
- Complete compromise of the affected server's confidentiality, integrity, and availability.
- Potential unauthorized access to sensitive data stored or processed on the server.
- Disruption of services running on the managed servers.
- Possibility for attackers to move laterally within the network or deploy further malicious payloads.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been patched in Termix version 2.1.0. The immediate step to mitigate this vulnerability is to upgrade Termix to version 2.1.0 or later.