Skip to content
Fencer Vulns
medium 5.3

CVE-2026-70607 json

Electron: window.open features string controls some window options considered privileged

published 2026-08-05 3 mo ago modified 2026-10-08 31 d ago also GHSA-v93f-fgjr-hjrj , EUVD-2026-53462

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
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.8, 40.9.0, 41.2.1, and 42.0.0-beta.3, some window options supplied by web content in the window.open() features string were applied to the new BrowserWindow without an allowlist. Untrusted content could set window options it should not control, including options that cause the main process to access attacker-chosen file or network paths, when untrusted content can call window.open() and the app does not override child window options via setWindowOpenHandler or overrideBrowserWindowOptions. This issue is fixed in 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.

Patch / fix

  • npm electron 39.8.8, 40.9.0, 41.2.1, 42.0.0-beta.3
  • electronjs electron 39.8.8, 40.9.0

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
npm electron
<39.8.8
>=40.0.0-alpha.1, <40.9.0
>=41.0.0-alpha.1, <41.2.1
>=42.0.0-alpha.1, <42.0.0-beta.3
39.8.8
40.9.0
41.2.1
42.0.0-beta.3

Affected products

  • electron electron

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns 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.