MediumGHSA-f2r8-jv7c-xqmpCVE-2026-70611

Electron: DevTools embedder handler executes arbitrary files via shell open

Published 5 Aug 2026 · Updated 5 Aug 2026

Affected packages

Affected
<39.8.9
Fixed in
39.8.9
Update to the fixed version for your release line, for example:npm install electron@39.8.9
Affected
>=40.0.0-alpha.1 <40.9.2
Fixed in
40.9.2
Update to the fixed version for your release line, for example:npm install electron@40.9.2
Affected
>=41.0.0-alpha.1 <41.2.1
Fixed in
41.2.1
Update to the fixed version for your release line, for example:npm install electron@41.2.1
Affected
>=42.0.0-alpha.1 <42.0.0-beta.3
Fixed in
42.0.0-beta.3
Update to the fixed version for your release line, for example:npm install electron@42.0.0-beta.3

Details

Impact

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.

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 [security@electronjs.org](mailto:security@electronjs.org)

Is GHSA-f2r8-jv7c-xqmp in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected electron, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.