Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3, the check Electron uses on macOS to confirm it was launched by a same-signed parent process could be bypassed by a local process. Apps that enable fuse-based hardening restricting ELECTRON_RUN_AS_NODE and NODE_OPTIONS to same-signed parents rely on this check, and a local attacker could bypass it and run code inside the signed app, inheriting its TCC permissions and keychain access. This issue is fixed in 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/electron/electron/commit/0a6291a97d210db3733689e70a51f5711e38ed35 Patch
- https://github.com/electron/electron/security/advisories/GHSA-jm7p-cc5g-qwxx Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.3 · electronjsNVD modified 2026-10-08 13:47
Affected (CPE criteria) 9
cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:42.0.0:alpha1:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:42.0.0:alpha2:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:42.0.0:alpha3:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:42.0.0:alpha4:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:42.0.0:alpha5:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:42.0.0:alpha6:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:42.0.0:beta1:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:42.0.0:beta2:*:*:*:node.js:*:*