Quick answers
- Is CVE-2026-34775 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34775 being exploited in the wild.
- How severe is CVE-2026-34775?
- Medium severity, with a CVSS score of 6.8, published 4 April 2026.
- Which products and versions are affected?
- electron (npm) SEMVER:introduced=0,fixed=38.8.6.
- Is there a fix for CVE-2026-34775?
- Yes. electron (npm): upgrade to 38.8.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34775 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-34775?
- Check whether you run electron (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
- electron (npm): upgrade to 38.8.6 or later
npm install electron@38.8.6
Technical details
An improper isolation vulnerability (CWE-653) exists in Electron's webPreferences handling. The 'nodeIntegrationInWorker' setting was not correctly scoped in scenarios where multiple frames share the same renderer process. Consequently, workers spawned in frames where 'nodeIntegrationInWorker' was explicitly set to false could still inherit Node.js integration if the parent or a sibling frame enabled it. An attacker who can execute code in a restricted frame might leverage this to gain full Node.js access, leading to remote code execution or data exfiltration. The issue is patched in versions 38.8.6, 39.8.4, 40.8.4, and 41.0.0.
Affected products
- ElectronJS Electron < 38.8.6, >= 39.0.0-alpha.1 < 39.8.4, >= 40.0.0-alpha.1 < 40.8.4, >= 41.0.0-alpha.1 < 41.0.0
Identifiers
- CVE-2026-34775
- GHSA-xwr5-m59h-vwqr
Timeline
- 2026-04-02: advisory: GitHub Security Advisory published
- 2026-04-03: disclosed: NVD publication date