Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.0amended

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

CVE-2026-34765GHSA-f3pv-wv63-48x8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 42.0.0-alpha.5, 41.1.0, 40.8.5, 39.8.5), 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
    < 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
    Fixed in
    39.8.5, 42.0.0-alpha.5, 40.8.5, 41.1.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.0 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
EPSS
  • CVE-2026-34765: 0.30% estimated exploitation activity in the next 30 days; percentile 22.74 (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 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…

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

    Amended from ghsa record GHSA-f3pv-wv63-48x8

  2. Revision 1 · created ·

    Published from osv record GHSA-f3pv-wv63-48x8

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-34765

Advisory: Electron: Named window.open targets not scoped to the opener's browsing context
IDs: CVE-2026-34765, GHSA-f3pv-wv63-48x8
Record: https://patchnext.com/advisories/cve-2026-34765 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 42.0.0-alpha.5, 41.1.0, 40.8.5, 39.8.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected < 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; fixed in 39.8.5, 42.0.0-alpha.5, 40.8.5, 41.1.0

## 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://osv.dev/vulnerability/GHSA-f3pv-wv63-48x8 (OSV record GHSA-f3pv-wv63-48x8 lists affected ranges: npm electron >=0 =40.0.0-alpha.1 =41.0.0-alpha.1 =42.0.0-alpha.1 <42.0.0-alpha.5 (fixed))
- Verified: https://github.com/advisories/GHSA-f3pv-wv63-48x8 (GitHub-reviewed advisory GHSA-f3pv-wv63-48x8 lists affected ranges: npm electron >=0 =40.0.0-alpha.1 =41.0.0-alpha.1 =42.0.0-alpha.1 <42.0.0-alpha.5)

Commands are suggestions: review each one before running it.

Loading voting…