CVE-2026-70611

Electron: DevTools embedder handler executes arbitrary files via shell open

Workarounds

Do not open DevTools for windows that load untrusted content, and do not load untrusted DevTools extensions.

Fixed Versions

• 42.0.0-beta.3
• 41.2.1
• 40.9.2
• 39.8.9

For more information

If you have any questions or comments about this advisory, email Electron at [email protected]

The DevTools "reveal in file manager" action could launch the target file rather than reveal it. An attacker with a separate means of running script inside the DevTools frontend (such as a malicious DevTools extension) could use this to execute native code outside the sandbox.

Apps are only affected if DevTools is opened for windows exposed to untrusted content or untrusted DevTools extensions. Apps that do not open DevTools in that context are not affected.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2026-70611 has a CVSS score of 6.9 (Medium). The vector is requires local access, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (39.8.9, 40.9.2, 41.2.1, 42.0.0-beta.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-70611? CVE-2026-70611 is a medium-severity OS command injection vulnerability in electron (npm), affecting versions < 39.8.9. It is fixed in 39.8.9, 40.9.2, 41.2.1, 42.0.0-beta.3. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2026-70611? CVE-2026-70611 has a CVSS score of 6.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of electron are affected by CVE-2026-70611? electron (npm) versions < 39.8.9 is affected.
4. Is there a fix for CVE-2026-70611? Yes. CVE-2026-70611 is fixed in 39.8.9, 40.9.2, 41.2.1, 42.0.0-beta.3. Upgrade to this version or later.
5. Is CVE-2026-70611 exploitable, and should I be worried? Whether CVE-2026-70611 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-70611 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-70611?
   • Upgrade electron to 39.8.9 or later
   • Upgrade electron to 40.9.2 or later
   • Upgrade electron to 41.2.1 or later
   • Upgrade electron to 42.0.0-beta.3 or later

Other vulnerabilities in electron