electron
Affected
- introduced
0, fixed39.8.5(semver)
Fixed versions
39.8.5
Fix
- Fixed version
39.8.5npm install [email protected]
Advisory
Also known as: CVE-2026-34765
Electron: Named window.open targets not scoped to the opener's browsing context
Impact
When a renderer calls window.open() with a target name, Electron did not correctly scope the named-window lookup to the opener's browsing context group. A renderer could navigate an existing child window that was opened by a different, unrelated renderer if both used the same target name. If that existing child was created with more permissive webPreferences (via setWindowOpenHandler's overrideBrowserWindowOptions), content loaded by the second renderer inherits those permissions.
Apps are only affected if they open multiple top-level windows with differing trust levels and use setWindowOpenHandler to grant child windows elevated webPreferences such as a privileged preload script. Apps that do not elevate child window privileges, or that use a single top-level window, are not affected.
Apps that additionally grant nodeIntegration: true or sandbox: false to child windows (contrary to the security recommendations) may be exposed to arbitrary code execution.
Workarounds
Deny window.open() in renderers that load untrusted content by returning { action: 'deny' } from setWindowOpenHandler. Avoid granting child windows more permissive webPreferences than their opener.
Fixed Versions
42.0.0-alpha.541.1.040.8.539.8.5For more information
If you have any questions or comments about this advisory, email us at [[email protected]](mailto:[email protected])
Medium Basis: The source's own band: MODERATE
0, fixed 39.8.5 (semver)39.8.5
39.8.5npm install [email protected]40.0.0-alpha.1, fixed 40.8.5 (semver)40.8.5
40.8.5npm install [email protected]41.0.0-alpha.1, fixed 41.1.0 (semver)41.1.0
41.1.0npm install [email protected]42.0.0-alpha.1, fixed 42.0.0-alpha.5 (semver)42.0.0-alpha.5
42.0.0-alpha.5npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0