CVE-2026-70608 json
Electron: Sandboxed iframe can bypass the allow-popups restriction via the OpenURL navigation path
published 3mo ago modified last mo. also EUVD-2026-53564 , GHSA-9f4c-93c8-jc8g
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.10, 41.10.3, and 42.0.1, 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, while apps that deny window creation in setWindowOpenHandler or do not embed untrusted content in sandboxed iframes are not affected. This issue is fixed in 39.8.10, 41.10.3, and 42.0.1.
Patch / fix
- npm electron 39.8.10, 41.10.3, 42.0.1
- atom electron 39.8.10, 41.10.3, 42.0.1
- electronjs electron 39.8.10, 41.10.3, 42.0.1
- github.com/electron/electron@3ff23c5 commit
- github.com/electron/electron@57cbe32 commit
- github.com/electron/electron@68cf8b7 commit
- github.com/electron/electron#51437 pull request
- github.com/electron/electron#51438 pull request
- github.com/electron/electron#51439 pull request
- github.com/electron/electron/releases/tag/v39.8.10 release
- github.com/electron/electron/releases/tag/v41.10.3 release
- github.com/electron/electron/releases/tag/v42.0.1 release
Is CVE-2026-70608 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | electron | >=42.0.0-alpha.1, <42.0.1 >=40.0.0-alpha.1, <41.10.3 <39.8.10 |
42.0.1 41.10.3 39.8.10 |
Affected products
- electron electron
Classification
References
-
github.com
/electron/electron/pull/51437
web, issue-tracking, patch
-
github.com
/electron/electron/pull/51438
web, issue-tracking, patch
-
github.com
/electron/electron/pull/51439
web, issue-tracking, patch
-
github.com
/electron/electron/commit/3ff23c52ab364a0afc6ab5bd7851291d3159de57
web, patch
-
github.com
/electron/electron/commit/57cbe329c4ae8aab5ac5ebdcb588adc9a11de0d3
web, patch
-
github.com
/electron/electron/commit/68cf8b7d9122260f6b534a69a82c701a56cf159f
web, patch
-
github.com
/electron/electron/security/advisories/GHSA-9f4c-93c8-jc8g
web, vendor-advisory, advisory
-
github.com
/electron/electron/releases/tag/v39.8.10
web, release-notes
-
github.com
/electron/electron/releases/tag/v41.10.3
web, release-notes
-
github.com
/electron/electron/releases/tag/v42.0.1
web, release-notes
-
github.com
/electron/electron
package
Sources
- CVE List CVE-2026-70608
- GitHub Advisory GHSA-9f4c-93c8-jc8g
- NVD CVE-2026-70608
- Maintainer advisory GHSA-9f4c-93c8-jc8g
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of electron/electron published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.