CVE-2026-70608: Electron: Sandboxed iframe can bypass the allow-popups restriction via the OpenURL navigation path

Published Aug 5, 2026
·
Updated

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

Other sources

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.

— MITRE

Affected Software

6 affected componentsFixes available
npm/electron<39.8.10
39.8.10
npm/electron>=40.0.0-alpha.1<41.10.3
41.10.3
npm/electron>=42.0.0-alpha.1<42.0.1
42.0.1
electronjs Electron Node.js<39.8.8
electronjs Electron Node.js>=40.0.0<41.10.3
electronjs Electron Node.js>=42.0.0<42.0.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 39.8.10
  2. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 41.10.3
  3. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 42.0.1
  4. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 39.8.10
  5. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 41.10.3
  6. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 42.0.1
  7. Configuration

    Return { action: 'deny' } from setWindowOpenHandler for any content you do not trust, rather than relying on the iframe sandbox alone.

    Electron setWindowOpenHandler = { action: 'deny' }

Event History

Aug 5, 2026
CVE Published
via MITRE·05:27 PM
Data Sourced
via MITRE·05:27 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·05:27 PM
Data Sourced
via GitHub·05:27 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·06:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-70608?

The severity of CVE-2026-70608 is high, with a score of 7.2.

2

How do I fix CVE-2026-70608?

To fix CVE-2026-70608, ensure that the `allow-popups` keyword is included in your iframe sandbox attributes.

3

What are the potential impacts of CVE-2026-70608?

CVE-2026-70608 could allow a sandboxed iframe to open new windows without user interaction, bypassing intended restrictions.

4

Which software is affected by CVE-2026-70608?

CVE-2026-70608 affects the Electron framework used for building cross-platform desktop applications.

5

Is user interaction required to exploit CVE-2026-70608?

No, exploitation of CVE-2026-70608 does not require user interaction.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203