CVE-2026-34765: Electron: Named window.open targets not scoped to the opener's browsing context
(updated )
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.
References
- github.com/advisories/GHSA-f3pv-wv63-48x8
- github.com/electron/electron
- github.com/electron/electron/releases/tag/v39.8.5
- github.com/electron/electron/releases/tag/v40.8.5
- github.com/electron/electron/releases/tag/v41.1.0
- github.com/electron/electron/releases/tag/v42.0.0-alpha.5
- github.com/electron/electron/security/advisories/GHSA-f3pv-wv63-48x8
- nvd.nist.gov/vuln/detail/CVE-2026-34765
Code Behaviors & Features
Detect and mitigate CVE-2026-34765 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →