electerm

CVE-2026-41500

CVE-2026-41500 is a critical-severity command injection vulnerability in electerm (npm), affecting versions < 3.3.8. It is fixed in 3.3.8.

Key facts
CVSS score
9.8
Critical
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
electerm
Fixed in
3.3.8
Disclosed
2026

Summary

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

Impact

What is command injection?

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

Severity and exposure

CVE-2026-41500 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. 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.3.8). Upgrading removes the vulnerable code path.

Affected versions

npm

  • electerm (< 3.3.8)

Security releases

  • electerm → 3.3.8 (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-41500 is reachable in your applications. Explore runtime application protection for your team.

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

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

Remediation advice

Upgrade electerm to 3.3.8 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-41500

What is CVE-2026-41500?

CVE-2026-41500 is a critical-severity command injection vulnerability in electerm (npm), affecting versions < 3.3.8. It is fixed in 3.3.8. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.

How severe is CVE-2026-41500?

CVE-2026-41500 has a CVSS score of 9.8 (Critical). 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-41500?

electerm (npm) versions < 3.3.8 is affected.

Is there a fix for CVE-2026-41500?

Yes. CVE-2026-41500 is fixed in 3.3.8. Upgrade to this version or later.

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

Whether CVE-2026-41500 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-41500 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-41500?

Upgrade electerm to 3.3.8 or later.

Stop the waste.
Protect your environment with Kodem.