Skip to content
Fencer Intel
medium 6.0

CVE-2026-34765 json

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

published 7mo ago modified 3mo ago also EUVD-2026-19949 , GHSA-f3pv-wv63-48x8

cvss
6.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5, 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. This vulnerability is fixed in 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5.

Patch / fix

  • npm electron 39.8.5, 40.8.5, 41.1.0, 42.0.0-alpha.5
  • atom electron 39.8.5, 40.8.5, 41.1.0, 42.0.0-alpha.5
  • electronjs electron 39.8.5, 40.8.5, 41.1.0, 42.0.0-alpha.5

Is CVE-2026-34765 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-34765 updated cvss 7.1

electron: Electron: Arbitrary code execution or information disclosure via incorrect window handling

  • Red Hat Build of Podman Desktop podman-desktop-macos-1-0, podman-desktop-windows-1-0 Red Hat Build of Podman Desktop - Tech Preview redhat-user-workloads/red-hat-desktop-tenant/openshift-local-ext Red Hat Enterprise Linux 10 podman-desktop, rh-podman-desktop
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
7mo ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
GitHub 3.1 6.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm 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

Affected products

  • electron electron

Classification

Weakness
  • CWE-668 Exposure of Resource to Wrong Sphere

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.