Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

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

CVE-2026-102674GHSA-gr2m-v5gq-v685

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 44.0.0-beta.5, 43.4.1, 42.9.2, 41.10.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm electron

    Affected
    < 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
    Fixed in
    42.9.2, 44.0.0-beta.5, 43.4.1, 41.10.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
EPSS
  • CVE-2026-102674: 0.24% estimated exploitation activity in the next 30 days; percentile 14.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Windows opened from a sandboxed top-level document did not inherit that document's HTML sandbox restrictions, so content that was meant to run sandboxed could open a window with the app's full origin. GHSA-hq2x-r82h-9wj4 covers the same issue for sandboxed iframes. Apps are only affected if they render untrusted content in a sandboxed top-level document that allows popups. Apps that deny popups from untrusted content with setWindowOpenHandler are not affected. Workarounds Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content. Fixed Versions 44.0.0-beta.5 43.4.1 42.9.2 41.10.6 For more information If you have any questions or comments about this advisory, email us at security@electronjs.org

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-gr2m-v5gq-v685

  2. Revision 2 · amended ·

    Amended from osv record GHSA-gr2m-v5gq-v685

  3. Revision 1 · created ·

    Published from ghsa record GHSA-gr2m-v5gq-v685

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102674

Advisory: Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions
IDs: CVE-2026-102674, GHSA-gr2m-v5gq-v685
Record: https://patchnext.com/advisories/cve-2026-102674 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 44.0.0-beta.5, 43.4.1, 42.9.2, 41.10.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected < 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; fixed in 42.9.2, 44.0.0-beta.5, 43.4.1, 41.10.6

## Suggested inspection (read-only)
- `npm ls electron --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gr2m-v5gq-v685 (GitHub-reviewed advisory GHSA-gr2m-v5gq-v685 lists affected ranges: npm electron >=0 =42.0.0-alpha.1 =43.0.0-alpha.1 =44.0.0-alpha.1 <44.0.0-beta.5)
- Verified: https://osv.dev/vulnerability/GHSA-gr2m-v5gq-v685 (OSV record GHSA-gr2m-v5gq-v685 lists affected ranges: npm electron >=0 =42.0.0-alpha.1 =43.0.0-alpha.1 =44.0.0-alpha.1 <44.0.0-beta.5 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…