CVE-2020-26272: electron · Resource Exposure
Affects electronSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 9.4.0 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.4.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jan 2021
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade electron/electron to 9.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubelectron/electronpkg:github/electron/electronOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The primary mitigation is to upgrade Electron to a patched version: 9.4.0 or later in the 9.x series, 10.2.0 or later in the 10.x series, or 11.1.0 or later in the 11.x series. Since no workarounds exist, patching is critical. Additionally, organizations should audit their Electron applications to identify usage of the remote module, webContents.sendToFrame, and event.reply IPC methods, minimizing or refactoring their use if possible to reduce attack surface. Implement strict frame isolation and validate IPC message recipients within the application code to ensure messages are delivered only to intended frames. Employ runtime monitoring to detect anomalous IPC message patterns. For Electron apps handling sensitive data, consider additional encryption or data validation layers within IPC communication. Finally, maintain an inventory of Electron-based applications and enforce timely updates as part of the software supply chain security practices.
Description
The Electron framework lets users write cross-platform desktop applications using JavaScript, HTML and CSS. In versions of Electron IPC prior to 9.4.0, 10.2.0, 11.1.0, and 12.0.0-beta.9, messages sent from the main process to a subframe in the renderer process, through webContents.sendToFrame, event.reply or when using the remote module, can in some cases be delivered to the wrong frame. If your app uses remote, calls webContents.sendToFrame, or calls event.reply in an IPC message handler then it is impacted by this issue. This has been fixed in versions 9.4.0, 10.2.0, 11.1.0, and 12.0.0-beta.9. There are no known workarounds for this issue.
References
- github.com/electron/electron/security/advisories/GHSA-hvf8-h2qh-37m9 (opens in a new tab)
- github.com/electron/electron/pull/26875 (opens in a new tab)
- github.com/electron/electron/commit/07a1c2a3e5845901f7e2eda9506695be58edc73c (opens in a new tab)
- github.com/electron/electron/commit/0bbd268eb4caf35604443df5ff196980dd49e208 (opens in a new tab)
- github.com/electron/electron/commit/36c695ce2a7e22c07fe1e30c61c00d20371daee2 (opens in a new tab)
- github.com/electron/electron/commit/429400040ecb16a21d19936658579e65a797e4cc (opens in a new tab)
- github.com/electron/electron/commit/5c8e7e8b7f485ceafa8b271086d7b87e1de9dedd (opens in a new tab)
- github.com/electron/electron/releases/tag/v9.4.0 (opens in a new tab)
- electronjs.org/releases/stable?version=9 (opens in a new tab)