Skip to content
Fencer Vulns
high 7.5

CVE-2026-70601 json

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

published 2026-08-05 3 mo ago modified 2026-10-08 31 d ago also GHSA-h7rp-cf8h-j98x , EUVD-2026-53433

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

Summary

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.

Patch / fix

  • npm electron 39.8.9, 40.9.2, 41.2.2, 42.0.0-beta.5
  • electronjs electron 39.8.9, 40.9.2, 41.2.2

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
npm electron
<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
39.8.9
40.9.2
41.2.2
42.0.0-beta.5

Affected products

  • electron electron

Classification

Weakness
  • CWE-693 Protection Mechanism Failure

References

Sources

Fencer Vulns 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.