CVE-2026-70608

highpriority · track · 0EPSS 0.004 · 36 %ileEUUS

grimoire priorityP2 · Scheduled

Exploitable?

—

no known exploitation

Likely / severe?

0.43% (36th) EPSS

CVSS 7.2 · high

Is it mine?

9 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-24

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.

cvss

Technical severity, 0–10. One row per scoring source.

7.2

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.6–7.2

v3.17.2highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:Nsecondary · ENISA EU

v3.17.2highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:Nsecondary · security-advisories@github.comexploitability 3.9 · impact 2.7

v3.17.2highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:Nsecondary · OSV

v3.16.6mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N/E:Usecondary · CVSS-BT (t0sche)

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: yes · Technical Impact: partialcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-1021USCWE-1021USCWE-693USCWE-693US

affected products (9)

Products and version ranges known to be affected.

Electron Electron≤ < 39.8.10enisa_euvdEU
Electron Electron40.0.0-alpha.1, → 41.10.3enisa_euvdEU
Electron Electron42.0.0-alpha.1, → 42.0.1enisa_euvdEU
electronjs electron< 39.8.8nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron40.0.0 → 41.10.3nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron42.0.0 → 42.0.1nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
npm electron< 39.8.10osvUSpkg:npm/electron
npm electron40.0.0-alpha.1 → 41.10.3osvUSpkg:npm/electron
npm electron42.0.0-alpha.1 → 42.0.1osvUSpkg:npm/electron

advisories (1)

Vendor and ecosystem advisories describing this.

GHSA-9f4c-93c8-jc8gElectron: Sandboxed iframe can bypass the allow-popups restriction via the OpenURL navigation path2026-08-05ghsa · osvUS
### 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.1` * `41.10.3` * `39.8.10` ### For more information If you have any questions or comments about this advisory, email Electron at [security@electronjs.org](mailto:security@electronjs.org)

also known as (3)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd nvd osv NVD CVE.org MITRE

published 2026-08-05modified 2026-08-05

references (31)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan