Quick answers
- Is CVE-2026-41501 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41501 being exploited in the wild.
- How severe is CVE-2026-41501?
- Critical severity, with a CVSS score of 9.8, published 8 May 2026.
- Which products and versions are affected?
- electerm (npm) < 3.3.8, SEMVER:introduced=0,fixed=3.3.8.
- Is there a fix for CVE-2026-41501?
- Yes. electerm (npm): upgrade to 3.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41501 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-41501?
- Check whether you run Electerm Project Electerm or electerm (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- electerm (npm): upgrade to 3.3.8 or later
npm install electerm@3.3.8
Technical details
A command injection vulnerability exists in the `runLinux()` function within `npm/install.js`. The application fails to validate or sanitize remote version strings retrieved from the update server before appending them to a system command executed via `exec("rm -rf ...")`. An attacker capable of manipulating the project's remote release metadata (such as the version string or release name) can inject malicious shell commands. This vulnerability is triggered when a user runs `npm install -g electerm` on a Linux platform. The issue is fixed in version 3.3.8.
Affected products
- electerm electerm < 3.3.8
Identifiers
- CVE-2026-41501
- GHSA-8x35-hph8-37hq
Timeline
- 2026-04-22: disclosed: Vulnerability reported to vendor
- 2026-04-24: advisory: GitHub Advisory published
- 2026-05-08: other: NVD published CVE-2026-41501