Command Injection in electerm-project (CVE-2026-41500, CVSS 9.8)

Summary

command injection in electerm-project (CVE-2026-41500). Successful exploitation can lead to full system takeover. Exploitable via releaseInfo.name. Mitigation: upgrade to > 3.2.0 or later.

Original description

The description as published by the source.

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:150. The runMac() function appends attacker-controlled remote releaseInfo.name directly into an exec("open ...") command without validation.

Who is impacted: Users who run npm install -g electerm in Mac OS. 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

References

Are there any links users can visit to find out more?

59708b38c8a52f5db59d7d4eff98e31d573128ee

Source: NIST National Vulnerability Database NVD GitHub Advisory

AI summary

Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.

A vulnerability in the electerm terminal client allows malicious actors to inject harmful commands into computers, particularly impacting Mac OS users installing via npm. This could lead to partial system takeover. The issue has been patched in the latest version 3.3.8, and users should update immediately.

The vulnerability in electerm involves a command injection in the runMac() function of github.com/elcterm/electerm/npm/install.js:150. Here, the attacker-controlled releaseInfo.name is inserted into an exec("open ...") command without proper validation. Affected versions are <=3.2.0, patched in 3.3.8. There are no workarounds; it is critical to update via npm install -g electerm. Detection is challenging, thus continuous monitoring of applied system logs is advised.

❓ What is the problem

Command injection vulnerability in electerm's runMac() function.

📍 Affected scope

github.com/elcterm/electerm/npm/install.js:150.

🔥 Severity

Critical severity (CVSS v3: 9.8, remote exploitation without authentication).

🔧 How to fix

Update to electerm version 3.3.8 via npm.

🛡️ Workaround

No workaround available.

🔍 Detection

Monitoring system logs for unusual entries post-update.

Related past incidents Similar incidents extracted from past CVEs

CVE-2021-3156

A similar sudo privilege escalation vulnerability affecting OS systems without proper input validation.

CVE-2014-6271

Shellshock bug, another shell command injection vulnerability resulting from improper input handling.

Log4Shell

Widely exploited vulnerability in Log4j for logging untrusted data, parallel to electerm's fault.

If this happens at your company Expected impact per business scenario

📌 Development environments using electerm for remote connections.

Unauthorized command execution could compromise sensitive source code and configuration files.

📌 Systems administrators managing servers over SSH via electerm.

Attackers may execute arbitrary commands, leading to potential server compromise.

📌 Organizations using electerm for telnet/sftp operations on Mac OS.

Unauthorized access and command execution could disrupt operations and lead to data integrity issues.

Recommended action

Promptly update electerm to version 3.3.8 and monitor systems for anomalies.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'electerm-project' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で electerm-project を grep し、稼働しているサービス・バージョンを把握する。
2
Match against affected range verify
```
Confirm if version satisfies `<=3.2.0`
```
Step 1 で見つかったバージョンが影響範囲 <=3.2.0 に該当するか照合。本番で稼働中ならインシデント扱い。
6
Apply patch patch
```
Upgrade electerm-project to > 3.2.0
```
ステージング環境で > 3.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm electerm

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.3.8"}]}]

References

advisory nvd.nist.gov
package github.com
web github.com
web github.com
web github.com
web github.com