CVE-2026-70608: Electron: Sandboxed iframe can bypass the allow-popups restriction via the OpenURL navigation path
Impact A sandboxed iframe without the allow-popups keyword could still open a new window (or trigger setWindowOpenHandler) with no user interaction, because new-window navigations taking the OpenURL path did not apply the iframe sandbox popup restriction. Apps that embed untrusted content in sandboxed iframes and rely on the absence of allow-popups to prevent window creation are affected.
Published Aug 5, 2026
Affected packages
electron
- Ecosystem
- npm
- Affected
- >= 42.0.0-alpha.1, < 42.0.1
- Fixed in
- 42.0.1
- Check
npm ls electron
electron
- Ecosystem
- npm
- Affected
- >= 40.0.0-alpha.1, < 41.10.3
- Fixed in
- 41.10.3
- Check
npm ls electron
electron
- Ecosystem
- npm
- Affected
- < 39.8.10
- Fixed in
- 39.8.10
- Check
npm ls electron
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A sandboxed iframe without the allow-popups keyword could still open a new window (or trigger setWindowOpenHandler) with no user interaction, because new-window navigations taking the OpenURL path did not apply the iframe sandbox popup restriction.
Apps that embed untrusted content in sandboxed iframes and rely on the absence of allow-popups to prevent window creation are affected. Apps that deny window creation in setWindowOpenHandler, or that do not embed untrusted content in sandboxed iframes, are not affected.
Workarounds
Return { action: 'deny' } from setWindowOpenHandler for any content you do not trust, rather than relying on the iframe sandbox alone.
Fixed Versions
42.0.141.10.339.8.10
For more information
If you have any questions or comments about this advisory, email Electron at [[email protected]](mailto:[email protected])
Credited to Ciarands.
References
- https://github.com/electron/electron/security/advisories/GHSA-9f4c-93c8-jc8g
- https://github.com/electron/electron/pull/51437
- https://github.com/electron/electron/pull/51438
- https://github.com/electron/electron/pull/51439
- https://github.com/electron/electron/commit/3ff23c52ab364a0afc6ab5bd7851291d3159de57
- https://github.com/electron/electron/commit/57cbe329c4ae8aab5ac5ebdcb588adc9a11de0d3
- https://github.com/electron/electron/commit/68cf8b7d9122260f6b534a69a82c701a56cf159f
- https://github.com/electron/electron/releases/tag/v39.8.10
- https://github.com/electron/electron/releases/tag/v41.10.3
- https://github.com/electron/electron/releases/tag/v42.0.1
- https://github.com/advisories/GHSA-9f4c-93c8-jc8g
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-115570
Electron: Mitigation for compromised eMudhra intermediate certificates
high7.4Oct 23, 2026CVE-2026-113796
Electron: SameSite cookie restrictions are not applied to windows opened from links
medium4.2Oct 22, 2026CVE-2026-113797
Electron: Extension tabs.query returns tab URLs and titles without the tabs permission
low3.1Oct 22, 2026CVE-2026-113798
Electron: Pointer lock permission requests can be attributed to the wrong frame
medium5.4Oct 22, 2026CVE-2026-114121
Electron: openExternal permission requests can be attributed to the wrong origin
medium5.4Oct 22, 2026CVE-2026-114122
Electron: Frame subscription trusts GPU-supplied frame geometry
low3.9Oct 22, 2026
