CVE-2026-70612: Electron: Sandboxed iframes can launch external protocol handlers

Published Aug 5, 2026
·
Updated

Impact Requests to open external protocol URLs from web content did not take iframe sandbox restrictions into account, so a sandboxed iframe could cause an OS-registered external application to be launched. The frame's sandbox state was also not made available to the app's permission handlers.

Apps are only affected if they render untrusted content in sandboxed iframes and grant the openExternal permission (granted by default when no setPermissionRequestHandler is installed). Apps whose permission handler denies openExternal for untrusted content are not affected.

Workarounds Install a setPermissionRequestHandler that denies the openExternal permission for untrusted content.

Fixed Versions 42.0.0-beta.3 41.2.1 40.9.0 39.8.8

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.8, 40.9.0, 41.2.1, and 42.0.0-beta.3, requests to open external protocol URLs from web content did not take iframe sandbox restrictions into account, so a sandboxed iframe could cause an OS-registered external application to be launched. The frame sandbox state was also not made available to the app permission handlers, affecting apps that render untrusted content in sandboxed iframes and grant the openExternal permission by default when no setPermissionRequestHandler is installed. This issue is fixed in 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.

— MITRE

Affected Software

15 affected componentsFixes available
npm/electron>=42.0.0-alpha.1<42.0.0-beta.3
42.0.0-beta.3
npm/electron>=41.0.0-alpha.1<41.2.1
41.2.1
npm/electron>=40.0.0-alpha.1<40.9.0
40.9.0
npm/electron<39.8.8
39.8.8
electronjs Electron Node.js<39.8.8
electronjs Electron Node.js>=40.0.0<40.9.0
electronjs Electron Node.js>=41.0.0<=41.2.1
electronjs Electron Node.js=42.0.0-alpha1
electronjs Electron Node.js=42.0.0-alpha2
electronjs Electron Node.js=42.0.0-alpha3
electronjs Electron Node.js=42.0.0-alpha4
electronjs Electron Node.js=42.0.0-alpha5
electronjs Electron Node.js=42.0.0-alpha6
electronjs Electron Node.js=42.0.0-beta1
electronjs Electron Node.js=42.0.0-beta2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 42.0.0-beta.3
  2. Upgrade

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

    Fixed in 41.2.1
  3. Upgrade

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

    Fixed in 40.9.0
  4. Upgrade

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

    Fixed in 39.8.8
  5. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 39.8.8
  6. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 40.9.0
  7. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 41.2.1
  8. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 42.0.0-beta.3
  9. Configuration

    Install a setPermissionRequestHandler that denies the openExternal permission for untrusted content.

    Electron openExternal permission = deny for untrusted content

Event History

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

Frequently Asked Questions

1

What is the severity of CVE-2026-70612?

CVE-2026-70612 has a medium severity score of 5.4.

2

How do I fix CVE-2026-70612?

To mitigate CVE-2026-70612, update to the latest version of Electron that addresses the vulnerability.

3

What software is affected by CVE-2026-70612?

CVE-2026-70612 affects the Electron framework used in various npm applications.

4

What is the impact of CVE-2026-70612?

CVE-2026-70612 allows sandboxed iframes to launch OS-registered external applications unintentionally.

5

Is there a workaround for CVE-2026-70612?

Implementing strict validation of external protocol URLs and reviewing iframe sandbox policies may serve as a temporary workaround for CVE-2026-70612.

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