Skip to content

electerm has Command Injection in File System Operations (rmrf, mv, cp)

High severity GitHub Reviewed Published May 29, 2026 in electerm/electerm • Updated Jul 2, 2026

Package

npm electerm (npm)

Affected versions

<= 3.11.0

Patched versions

3.11.11

Description

Impact

A command injection vulnerability exists in electerm's file system operations (rmrf, mv, cp) in src/app/lib/fs.js. These functions construct shell commands by interpolating file paths directly into command strings without escaping shell metacharacters.

Vulnerable functions:

  • rmrf() - Uses rm -rf "${path}" (double quotes, vulnerable to " injection)
  • mv() - Uses mv '${from}' '${to}' (single quotes, vulnerable to ' injection)
  • cp() - Uses cp -r "${from}" "${to}" (double quotes, vulnerable to " injection)

Attack scenario:

  1. Attacker controls a malicious SSH/SFTP server
  2. Server lists files with shell metacharacters in names (e.g., file"$(touch /tmp/pwned)")
  3. Victim connects to the server and performs file operations (remote-to-local transfer, rename on conflict, etc.)
  4. The malicious filename is passed to rmrf(), mv(), or cp() without sanitization
  5. Shell metacharacters break out of the quoted argument and execute arbitrary commands

Impact includes:

  • Arbitrary command execution as the electerm desktop user
  • Data exfiltration, malware installation, or system compromise
  • Both POSIX (bash) and Windows (PowerShell) platforms are affected

Patches

Workarounds

If upgrading is not immediately possible, users can mitigate this vulnerability by:

  1. Only connecting to trusted SSH/SFTP servers
  2. Avoiding remote-to-local file transfers from untrusted sources
  3. Not using the "rename on conflict" option when downloading folders from untrusted servers
  4. Manually verifying filenames before performing file operations

References

@zxdong262 zxdong262 published to electerm/electerm May 29, 2026
Published to the GitHub Advisory Database Jul 2, 2026
Reviewed Jul 2, 2026
Last updated Jul 2, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(22nd percentile)

Weaknesses

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

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. Learn more on MITRE.

CVE ID

CVE-2026-49255

GHSA ID

GHSA-v5ff-xmfp-p245

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.