dbcve.org
ElectermApplication · Electerm Project

CVE-2026-41500

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 3.3.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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:150. The runMac() function appends attacker-controlled remote releaseInfo.name directly into an exec("open ...") command without validation. This issue has been patched in version 3.3.8.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in the electerm installer script (npm/install.js) where the runMac() function at line 150 directly passes attacker-controlled GitHub release metadata (releaseInfo.name) into an exec('open ...') call without any sanitization. An attacker who controls the release name on the electerm GitHub releases page can inject arbitrary shell commands that execute on victims' machines during the installation process.

MitigationUpgrade to electerm version 3.3.8 or later, which implements proper input validation before passing release information to shell execution functions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ElectermApplication
Affected:< 3.3.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if electerm is installed
    Look for electerm application in your system: On macOS check /Applications for electerm.app, on Linux check /opt or ~/electerm, on Windows check Program Files. Also check if 'electerm' command is available by running 'which electerm' (Linux/macOS) or where electerm (Windows).
    Affected if electerm is found installed on the system
  2. Identify installed electerm version
    Run 'electerm --version' or check the version within the application. On macOS, you can right-click electerm.app > Get Info to see the version. On Linux, check /opt/electerm/resources/app/package.json or the installed npm package with 'npm list electerm'.
    Affected if The installed version is lower than 3.3.8 (e.g., 3.3.7, 3.3.6, etc.)
  3. Locate the installer script
    Check for the presence of the file 'npm/install.js' within the electerm installation directory. Common paths: /Applications/electerm.app/Contents/Resources/app/npm/install.js (macOS) or /opt/electerm/resources/app/npm/install.js (Linux).
    Affected if The installer script file exists in the installation directory
  4. Inspect the runMac function for unsanitized input
    Open the install.js file and locate the runMac() function around line 150. Look for exec('open ...') calls where releaseInfo.name or similar GitHub release metadata is passed directly without validation or sanitization.
    Affected if The code shows exec() calls with releaseInfo.name passed directly without sanitization, and the version is below 3.3.8

You are affected if electerm is installed with a version lower than 3.3.8 and the installer script contains unsanitized GitHub release metadata passed to shell execution functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.3.8 or later
Fixed in 3.3.8
Vendor patch github.com →
Interim mitigation

Upgrade to electerm version 3.3.8 or later, which implements proper input validation before passing release information to shell execution functions.

Recommended fix High confidence

electerm version 3.3.8 or later

  1. Check current installed version of electerm (e.g., via `electerm --version` or within the application's about/info section)
  2. Upgrade electerm to version 3.3.8 or later. This can typically be done via: npm install -g [email protected] (if installed globally via npm), or by downloading the latest release from the official electerm releases page at https://github.com/electerm/electerm/releases
  3. After upgrading, verify the new version is installed and the application launches successfully

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Electerm Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41500 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41500 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data