Electron: Context isolation bypass via Function.prototype.bind hijack
Published 5 Aug 2026 · Updated 5 Aug 2026
Affected packages
- Affected
- <39.8.9
- Fixed in
- 39.8.9
npm install electron@39.8.9- Affected
- >=40.0.0-alpha.1 <40.9.2
- Fixed in
- 40.9.2
npm install electron@40.9.2- Affected
- >=41.0.0-alpha.1 <41.2.2
- Fixed in
- 41.2.2
npm install electron@41.2.2- Affected
- >=42.0.0-alpha.1 <42.0.0-beta.5
- Fixed in
- 42.0.0-beta.5
npm install electron@42.0.0-beta.5Details
Impact
Apps that expose Promise-returning functions to web content via contextBridge may be vulnerable to a context isolation bypass. Untrusted web content could obtain access to the isolated preload world and, through it, every capability the preload script has. In renderers without a sandbox, or with nodeIntegration enabled, this may escalate to Node.js access.
Apps are affected if they expose Promise-returning functions via contextBridge — the standard pattern for wrapping ipcRenderer.invoke — in windows that load untrusted content. Apps that never load untrusted content in those windows are not affected.
Workarounds
There are no app side workarounds, you must update to a patched version of Electron.
Fixed Versions
42.0.0-beta.541.2.240.9.239.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-h7rp-cf8h-j98x 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.