Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Electron: Context isolation bypass via Function.prototype.bind hijack

CVE-2026-70601GHSA-h7rp-cf8h-j98x

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 42.0.0-beta.5, 41.2.2, 40.9.2, 39.8.9), 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.9>= 40.0.0-alpha.1, < 40.9.2>= 41.0.0-alpha.1, < 41.2.2>= 42.0.0-alpha.1, < 42.0.0-beta.5
    Fixed in
    39.8.9, 40.9.2, 42.0.0-beta.5, 41.2.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS
  • CVE-2026-70601: 0.29% estimated exploitation activity in the next 30 days; percentile 21.12 (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 Apps that expose Promise-returning functions to web content via contextBridge may be vulnerable to a context isolation bypass. Untrusted web content could obtain access to the isolated preload world and, through it, every capability the preload script has. In renderers without a sandbox, or with nodeIntegration enabled, this may escalate to Node.js access. Apps are affected if they expose Promise-returning functions via contextBridge — the standard pattern for wrapping ipcRenderer.invoke — in windows that load untrusted content. Apps that never load untrusted content in those windows are not affected. Workarounds There are no app side workarounds, you must update to a patched version of Electron. Fixed Versions 42.0.0-beta.5 41.2.2 40.9.2 39.8.9 For more information If you have any questions or comments about this advisory, email Electron at security@electronjs.org

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

    Published from ghsa record GHSA-h7rp-cf8h-j98x

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

Advisory: Electron: Context isolation bypass via Function.prototype.bind hijack
IDs: CVE-2026-70601, GHSA-h7rp-cf8h-j98x
Record: https://patchnext.com/advisories/cve-2026-70601 (revision 1, source checked 26 Oct 2026, 13:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
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-beta.5, 41.2.2, 40.9.2, 39.8.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected < 39.8.9; >= 40.0.0-alpha.1, < 40.9.2; >= 41.0.0-alpha.1, < 41.2.2; >= 42.0.0-alpha.1, < 42.0.0-beta.5; fixed in 39.8.9, 40.9.2, 42.0.0-beta.5, 41.2.2

## 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-h7rp-cf8h-j98x (GitHub-reviewed advisory GHSA-h7rp-cf8h-j98x lists affected ranges: npm electron >=0 =40.0.0-alpha.1 =41.0.0-alpha.1 =42.0.0-alpha.1 <42.0.0-beta.5)

Commands are suggestions: review each one before running it.

Loading voting…