electerm

CVE-2026-49255

CVE-2026-49255 is a high-severity OS command injection vulnerability in electerm (npm), affecting versions <= 3.11.0. It is fixed in 3.11.11.

Key facts
CVSS score
8.8
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
electerm
Fixed in
3.11.11
Disclosed
2026

Summary

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: Attacker controls a malicious SSH/SFTP server Server lists files with shell metacharacters in names (e.g., file"$(touch /tmp/pwned)") Victim connects to the server and performs file operations (remote-to-local transfer, rename on conflict, etc.) The malicious filename is passed to rmrf(), mv(), or cp() without sanitization 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 https://github.com/electerm/electerm/commit/aa778818843b9c083bd711cd04644d102fcb5a42 Workarounds If upgrading is not immediately possible, users can mitigate this vulnerability by: Only connecting to trusted SSH/SFTP servers Avoiding remote-to-local file transfers from untrusted sources Not using the "rename on conflict" option when downloading folders from untrusted servers Manually verifying filenames before performing file operations

Impact

What is OS command injection?

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

Severity and exposure

CVE-2026-49255 has a CVSS score of 8.8 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (3.11.11). Upgrading removes the vulnerable code path.

Affected versions

npm

  • electerm (<= 3.11.0)

Security releases

  • electerm → 3.11.11 (npm)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's Application Detection and Response identifies whether CVE-2026-49255 is reachable in your applications. Explore runtime application protection for your team.

See if CVE-2026-49255 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-49255 in your environment

Remediation advice

Upgrade electerm to 3.11.11 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-49255

What is CVE-2026-49255?

CVE-2026-49255 is a high-severity OS command injection vulnerability in electerm (npm), affecting versions <= 3.11.0. It is fixed in 3.11.11. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

How severe is CVE-2026-49255?

CVE-2026-49255 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of electerm are affected by CVE-2026-49255?

electerm (npm) versions <= 3.11.0 is affected.

Is there a fix for CVE-2026-49255?

Yes. CVE-2026-49255 is fixed in 3.11.11. Upgrade to this version or later.

Is CVE-2026-49255 exploitable, and should I be worried?

Whether CVE-2026-49255 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-49255 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-49255?

Upgrade electerm to 3.11.11 or later.

Stop the waste.
Protect your environment with Kodem.