CVE-2026-70601

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

HIGH
7.5
CVSS Score
Published: August 5, 2026 at 03:45 PM UTC
Updated: October 8, 2026 at 01:54 PM UTC
2 products affected across 2 vendorsElectronElectron

Using electron by electron?

Get instant alerts when new vulnerabilities affect electron - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.9, 40.9.2, 41.2.2, and 42.0.0-beta.5, 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. This issue is fixed in versions 39.8.9, 40.9.2, 41.2.2, and 42.0.0-beta.5.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 39.8.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 40.9.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 41.2.2, so it looks safe — our inference, not a vendor statement
v < 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
Affected range stops below 39.8.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 40.9.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 41.2.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 42.0.0-beta.5, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_CONFIRMVendor Advisory
Source: cverecord
https://github.com/electron/electron/security/advisories/GHSA-h7rp-cf8h-j98x

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-693

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card