Medium

Electron: Named window.open targets not scoped to the opener's browsing context

  • Disclosed: 07.04.2026
  • Updated: 11.10.2026 10:22

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.5
  • 41.1.0
  • 40.8.5
  • 39.8.5

For more information

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

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package electron < 39.8.5, >= 40.0.0-alpha.1, < 40.8.5, >= 41.0.0-alpha.1, < 41.1.0, >= 42.0.0-alpha.1, < 42.0.0-alpha.5 39.8.5, 40.8.5, 41.1.0, 42.0.0-alpha.5

References

CVSS score 6/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
Weakness (CWE)
CWE-668
Platform
npm
Package
electron
Disclosed
07.04.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-f3pv-wv63-48x8 - CC BY 4.0

Vulnerability history: electron

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (71) in the archive
Total entries
71
First → latest
10.2017 09.2026
Without a fix
0
Exploited in attacks
3

Severity breakdown

  • Critical 3
  • High 26
  • Medium 32
  • Low 10

Disclosures per year

  1. 2017: 1
  2. 2018: 5
  3. 2019: 0
  4. 2020: 6
  5. 2021: 2
  6. 2022: 7
  7. 2023: 6
  8. 2024: 0
  9. 2025: 3
  10. 2026: 41
Severity:
  1. High · 8.2 CVE-2026-102673 < 41.10.4, >= 42.0.0-alpha.1, < 42.5.2, >= 43.0.0-alpha.1, < 43.0.0 41.10.4, 42.5.2, 43.0.0
  2. High · 8.2 CVE-2026-102674 < 41.10.6, >= 42.0.0-alpha.1, < 42.9.2, >= 43.0.0-alpha.1, < 43.4.1, >= 44.0.0-alpha.1, < 44.0.0-beta.5 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  3. High · 7.4 CVE-2026-102675 < 41.10.6, >= 42.0.0-alpha.1, < 42.9.2, >= 43.0.0-alpha.1, < 43.4.1, >= 44.0.0-alpha.1, < 44.0.0-beta.5 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  4. High · 8.3 CVE-2026-102676 < 41.10.6, >= 42.0.0-alpha.1, < 42.9.2, >= 43.0.0-alpha.1, < 43.4.1, >= 44.0.0-alpha.1, < 44.0.0-beta.5 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  5. High · 7.8 CVE-2026-102677 >= 42.3.3, < 42.10.0, >= 43.0.0-beta.1, < 43.5.0, >= 44.0.0-alpha.1, < 44.0.0-beta.6 42.10.0, 43.5.0, 44.0.0-beta.6
  6. High · 7.2 CVE-2026-70608 >= 42.0.0-alpha.1, < 42.0.1, >= 40.0.0-alpha.1, < 41.10.3, < 39.8.10 42.0.1, 41.10.3, 39.8.10
  7. High · 7.4 CVE-2026-70604 >= 42.0.0-alpha.1, < 42.0.0, >= 41.0.0-alpha.1, < 41.4.0, >= 40.0.0-alpha.1, < 40.9.3, < 39.8.10 42.0.0, 41.4.0, 40.9.3, 39.8.10
  8. High · 7.5 CVE-2026-70601 < 39.8.9, >= 40.0.0-alpha.1, < 40.9.2, >= 41.0.0-alpha.1, < 41.2.2, >= 42.0.0-alpha.1, < 42.0.0-beta.5 39.8.9, 40.9.2, 41.2.2, 42.0.0-beta.5
  9. Electron: Named window.open targets not scoped to the opener's browsing context this entry
    Medium · 6.0 CVE-2026-34765 < 39.8.5, >= 40.0.0-alpha.1, < 40.8.5, >= 41.0.0-alpha.1, < 41.1.0, >= 42.0.0-alpha.1, < 42.0.0-alpha.5 39.8.5, 40.8.5, 41.1.0, 42.0.0-alpha.5
  10. High · 8.3 CVE-2026-34780 >= 39.0.0-alpha.1, < 39.8.0, >= 40.0.0-alpha.1, < 40.7.0, >= 41.0.0-alpha.1, < 41.0.0-beta.8 39.8.0, 40.7.0, 41.0.0-beta.8
  11. High · 8.1 CVE-2026-34774 < 39.8.1, >= 40.0.0-alpha.1, < 40.7.0, >= 41.0.0-alpha.1, < 41.0.0 39.8.1, 40.7.0, 41.0.0
  12. High · 7.5 CVE-2026-34771 < 38.8.6, >= 39.0.0-alpha.1, < 39.8.0, >= 40.0.0-alpha.1, < 40.7.0, >= 41.0.0-alpha.1, < 41.0.0-beta.8 38.8.6, 39.8.0, 40.7.0, 41.0.0-beta.8
  13. High · 7.0 CVE-2026-34770 < 38.8.6, >= 39.0.0-alpha.1, < 39.8.1, >= 40.0.0-alpha.1, < 40.8.0, >= 41.0.0-alpha.1, < 41.0.0-beta.8 38.8.6, 39.8.1, 40.8.0, 41.0.0-beta.8
  14. High · 7.7 CVE-2026-34769 < 38.8.6, >= 39.0.0-alpha.1, < 39.8.0, >= 40.0.0-alpha.1, < 40.7.0, >= 41.0.0-alpha.1, < 41.0.0-beta.8 38.8.6, 39.8.0, 40.7.0, 41.0.0-beta.8
  15. High · 7.8 CVE-2024-46992 >= 30.0.0-alpha.1, < 30.0.5, >= 31.0.0-alpha.1, < 31.0.0-beta.1 30.0.5, 31.0.0-beta.1
  16. High · 8.8 Exploited in attacks CVE-2023-5217 < 22.3.25, >= 24.0.0, < 24.8.5, >= 25.0.0, < 25.8.4, >= 26.0.0, < 26.2.4, >= 27.0.0-alpha.1, < 27.0.0-beta.8 22.3.25, 24.8.5, 25.8.4, 26.2.4, 27.0.0-beta.8
  17. High · 8.8 Exploited in attacks CVE-2023-4863 >= 22.0.0, < 22.3.24, >= 24.0.0, < 24.8.3, >= 25.0.0, < 25.8.1, >= 26.0.0, < 26.2.1, >= 27.0.0-beta.1, < 27.0.0-beta.2 22.3.24, 24.8.3, 25.8.1, 26.2.1, 27.0.0-beta.2
  18. High · 7.5 CVE-2023-23623 >= 22.0.0-beta.1, < 22.0.1, >= 23.0.0-alpha.1, < 23.0.0-alpha.2 22.0.1, 23.0.0-alpha.2
  19. Critical · 9.6 Exploited in attacks CVE-2022-4135 >= 19.0.0, < 19.1.8 19.1.8
  20. High · 8.1 CVE-2017-12581 < 1.6.8 1.6.8
  21. High · 7.5 CVE-2020-15174 >= 8.0.0-beta.0, < 8.5.1, >= 9.0.0-beta.0, < 9.3.0, >= 10.0.0-beta.0, < 10.0.1 8.5.1, 9.3.0, 10.0.1
  22. High · 7.7 CVE-2020-4077 < 7.2.4, >= 8.0.0, < 8.2.4 7.2.4, 8.2.4
  23. High · 7.8 CVE-2020-4076 < 7.2.4, >= 8.0.0, < 8.2.4 7.2.4, 8.2.4
  24. High · 8.1 CVE-2018-15685 >= 1.7.0, < 1.7.16, >= 1.8.0, < 1.8.8, >= 2.0.0, < 2.0.8, >= 3.0.0-beta.1, < 3.0.0-beta.7 1.7.16, 1.8.8, 2.0.8, 3.0.0-beta.7
  25. Critical · 9.8 CVE-2017-16151 < 1.6.14, >= 1.7.0, < 1.7.8 1.6.14, 1.7.8
  26. High · 8.8 CVE-2018-1000118 < 1.8.2-beta5 1.8.2-beta5
  27. High · 8.1 CVE-2018-1000136 >= 1.7.0, < 1.7.13, >= 1.8.0, < 1.8.4, >= 2.0.0-beta.1, < 2.0.0-beta.5 1.7.13, 1.8.4, 2.0.0-beta.5
  28. High · 8.8 CVE-2018-1000006 >= 1.7.0, < 1.7.11, >= 1.6.0, < 1.6.16, >= 1.8.0, < 1.8.2-beta.4 1.7.11, 1.6.16, 1.8.2-beta.4
  29. High · 7.8 CVE-2016-1202 < 0.33.5 0.33.5

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.