Quick answers
- Is CVE-2026-45353 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45353 being exploited in the wild.
- How severe is CVE-2026-45353?
- High severity, with a CVSS score of 7.8, published 28 May 2026.
- Which products and versions are affected?
- electerm (npm) >= 3.0.6, <= 3.8.8, SEMVER:introduced=3.0.6,fixed=3.9.0.
- Is there a fix for CVE-2026-45353?
- Yes. electerm (npm): upgrade to 3.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45353 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-45353?
- Check whether you run 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.9.0 or later
npm install electerm@3.9.0
Technical details
A local code execution vulnerability exists in Electerm due to improper verification of the source of communication on its single-instance socket/pipe. Any process running under the same user context can send a crafted JSON payload to this socket, which Electerm processes without UI interaction. This can be exploited to create new tabs and spawn attacker-controlled local processes. The issue is rooted in improper permission assignment (CWE-732) and improper verification of the communication channel (CWE-940). A fix is available in version 3.9.0.
Affected products
- electerm electerm >= 3.0.6, <= 3.8.8
Identifiers
- CVE-2026-45353
- GHSA-7p5m-v798-f8vv
Timeline
- 2026-05-12: disclosed
- 2026-05-14: advisory
- 2026-05-14: patched