Security Digest · Vulnerability record

CVE-2026-45353: Electerm Local code through electerm's single-instance socket

electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client.

CVSS 9.3 Critical EPSS 0.2% · p6

Should you act?

Critical, preconditions apply

Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.2%, percentile 6: FIRST’s model estimates a 0.2% chance of exploitation activity in the next 30 days, higher than 6% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Needs local access needed. Lower urgency for most teams unless an attacker could already run code on the machine.
  • Only applies if your dependency tree includes electerm (npm) >= 3.0.6, <= 3.8.8, fixed in 3.9.0. Check your lockfile, including transitive dependencies.

What it is

electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. From 3.0.6 to 3.8.8, This vulnerability is fixed in 3.9.0.

From the GitHub advisory

Impact Local code execution without UI interaction: any same-user process can send a JSON payload to electerm's single-instance socket/pipe, causing the app to create tabs and potentially spawn attacker-controlled local processes. Affects electerm single-instance installs on the machine.

Patches

- https://github.com/electerm/electerm/commit/0599e67069b00e376a2e962649aaad6096e63507

Workarounds

- Do not run unsafe command

Weakness type: CWE-94, CWE-732, CWE-940.

Product: electerm (npm) · Assigned by: GitHub_M · Published: 2026-05-28

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
npmelecterm>= 3.0.6, <= 3.8.83.9.0
VendorProductAffected versions (per CVE record)
electermelecterm>= 3.0.6, < 3.89.0

Severity scores

Scored byCVSSScoreVector
GitHub_M4.09.3 CriticalCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
GitHub4.09.3 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
  • Attack vector: local access needed
  • Attack complexity: low
  • Attack requirements: none
  • Privileges required: low (any account)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 0.17% probability of exploitation activity in the next 30 days; percentile 6.

Timeline

  • — GitHub-reviewed advisory GHSA-7p5m-v798-f8vv published (critical)
  • — CVE record last updated
  • — CVE record published by GitHub_M

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-7p5m-v798-f8vv github.com
  2. CVE.org record CVE-2026-45353 cve.org
  3. NVD entry CVE-2026-45353 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com

Critical npm advisories · Today’s Security Digest