Context isolation bypass in Electron
Published 6 Oct 2020 · Updated 8 Jul 2026
Affected packages
- Affected
- >=8.0.0-beta.0 <8.5.2
- Fixed in
- 8.5.2
npm install electron@8.5.2- Affected
- >=9.0.0-beta.0 <9.3.1
- Fixed in
- 9.3.1
npm install electron@9.3.1- Affected
- >=10.0.0-beta.0 <10.1.2
- Fixed in
- 10.1.2
npm install electron@10.1.2- Affected
- >=11.0.0-beta.0 <11.0.0-beta.6
- Fixed in
- 11.0.0-beta.6
npm install electron@11.0.0-beta.6Details
Impact
Apps using both contextIsolation and sandbox: true are affected.
Apps using both contextIsolation and nativeWindowOpen: true are affected.
This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.
Workarounds
There are no app-side workarounds, you must update your Electron version to be protected.
Fixed Versions
11.0.0-beta.610.1.29.3.18.5.2
For more information
If you have any questions or comments about this advisory:
- Email us at [security@electronjs.org](mailto:security@electronjs.org)
Is GHSA-56pc-6jqp-xqj8 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.