GHSA-gr2m-v5gq-v685: High severity npm/electron vulnerability

Published Sep 29, 2026
·
Updated

Impact

Windows opened from a sandboxed top-level document did not inherit that document's HTML sandbox restrictions, so content that was meant to run sandboxed could open a window with the app's full origin. GHSA-hq2x-r82h-9wj4 covers the same issue for sandboxed iframes.

Apps are only affected if they render untrusted content in a sandboxed top-level document that allows popups. Apps that deny popups from untrusted content with setWindowOpenHandler are not affected.

Workarounds

Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content.

Fixed Versions

44.0.0-beta.5 43.4.1 42.9.2 41.10.6

For more information

If you have any questions or comments about this advisory, email us at security@electronjs.org

Affected Software

4 affected componentsFixes available
npm/electron>=44.0.0-alpha.1<44.0.0-beta.5
44.0.0-beta.5
npm/electron>=43.0.0-alpha.1<43.4.1
43.4.1
npm/electron>=42.0.0-alpha.1<42.9.2
42.9.2
npm/electron<41.10.6
41.10.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 44.0.0-beta.5
  2. Upgrade

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

    Fixed in 43.4.1
  3. Upgrade

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

    Fixed in 42.9.2
  4. Upgrade

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

    Fixed in 41.10.6
  5. Configuration

    Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content.

    Electron setWindowOpenHandler = return { action: 'deny' }

Event History

Sep 29, 2026
Advisory Published
via GitHub·06:05 PM
Data Sourced
via GitHub·06:05 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications are affected only if they render untrusted content in a sandboxed top-level document and allow that content to open popups. Applications that deny popups from untrusted content through setWindowOpenHandler are not affected.

2

What does an attacker need to exploit it?

An attacker needs their untrusted content to be rendered in a sandboxed top-level document that permits popups, and must induce a user interaction to open a window. The opened window can then have the application's full origin rather than inheriting the sandbox restrictions.

3

What can be done while patching is not possible?

Configure setWindowOpenHandler to return { action: 'deny' } for windows opened by untrusted content. This prevents the popup behavior required for exploitation.

4

Which Electron releases contain fixes?

Fixed releases are 44.0.0-beta.5, 43.4.1, 42.9.2, and 41.10.6.

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