CVE-2026-41501: electerm has Command Injection Vulnerability via runLinux function
Impact What kind of vulnerability is it? Who is impacted?
Command Injection vulnerabilities in electerm:
A command injection vulnerability exists in github.com/elcterm/electerm/npm/install.js:130. The runLinux() function appends attacker-controlled remote version strings directly into an exec("rm -rf ...") command without validation.
Who is impacted: Users who run npm install -g electerm in Linux. An attacker who can control the remote release metadata (version string or release name) served by the project's update server could execute arbitrary system commands, tamper local files, and escalate compromise of development/runtime assets.
---
Patches Has the problem been patched? What versions should users upgrade to?
Fixed in 59708b38c8a52f5db59d7d4eff98e31d573128ee, user no need to upgrade, the new version already published in npm
---
Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading?
no
Other sources
electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. Prior to version 3.3.8, a command injection vulnerability exists in github.com/elcterm/electerm/npm/install.js:130. The runLinux() function appends attacker-controlled remote version strings directly into an exec("rm -rf ...") command without validation. This issue has been patched in version 3.3.8.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41501?
CVE-2026-41501 is a command injection vulnerability that can allow an attacker to execute arbitrary commands on the affected system.
How does CVE-2026-41501 impact users?
Users of the electerm package may be exposed to remote command execution attacks due to the vulnerability.
How do I fix CVE-2026-41501?
To mitigate CVE-2026-41501, upgrade to electerm version 3.3.8 or later.
What versions of electerm are affected by CVE-2026-41501?
CVE-2026-41501 affects electerm versions prior to 3.3.8.
Where can I find more information about CVE-2026-41501?
Further details on CVE-2026-41501 can be found in the project's advisory documentation on their official repository.