HighGHSA-gr2m-v5gq-v685CVE-2026-102674

Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions

Published 29 Sept 2026 · Updated 29 Sept 2026

Affected packages

Affected
<41.10.6
Fixed in
41.10.6
Update to the fixed version for your release line, for example:npm install electron@41.10.6
Affected
>=42.0.0-alpha.1 <42.9.2
Fixed in
42.9.2
Update to the fixed version for your release line, for example:npm install electron@42.9.2
Affected
>=43.0.0-alpha.1 <43.4.1
Fixed in
43.4.1
Update to the fixed version for your release line, for example:npm install electron@43.4.1
Affected
>=44.0.0-alpha.1 <44.0.0-beta.5
Fixed in
44.0.0-beta.5
Update to the fixed version for your release line, for example:npm install electron@44.0.0-beta.5

Details

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](mailto:security@electronjs.org)

Is GHSA-gr2m-v5gq-v685 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected electron, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.