Skip to content
Fencer Intel
high 8.2

CVE-2026-102674 json

Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions

published last mo. modified 25d ago also EUVD-2026-89091 , GHSA-gr2m-v5gq-v685

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

Summary

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5, windows opened from a sandboxed top-level document did not inherit that document's active HTML sandbox restrictions. Untrusted content in a sandboxed top-level document that was permitted to open popups could therefore create a window with the Electron application's full origin instead of the restricted origin intended by the sandbox. Applications that deny such popups with setWindowOpenHandler are not affected. This issue is fixed in versions 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5.

Patch / fix

  • npm electron 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  • atom electron 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  • electronjs electron 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5

Is CVE-2026-102674 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-102674 updated cvss 8.2

electron: Electron: Sandbox bypass via popup window creation

  • Red Hat Build of Podman Desktop rh-podman-desktop 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
partial
Assessed
last mo.

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
GitHub 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

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

Affected products

  • electron electron

Classification

Weakness
  • CWE-266 Incorrect Privilege Assignment
  • CWE-693 Protection Mechanism Failure

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.