CVE-2020-26272mediumCWE-668

CVE-2020-26272: medium-severity vulnerability in electron

Electron vulnerable to ID collision when routing IPC messages to renderers containing OOPIFs

Published 28 Jan 2021 · Updated 27 May 2025

13Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 5.4epss 1.7%

exploitation probability

1.7%top 23% of all CVEs

observed exploitation

nono source reports it

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.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

Affected products

electron · electron

Related CVEs — electron

In the same product, most dangerous first.

CVE-2020-15174HIGHUnpreventable top-level navigation in ElectronEPSS 1.3%CVE-2020-4075MEDIUMArbitrary file read via window-open IPC in ElectronEPSS 1.2%CVE-2021-39184MEDIUMSandboxed renderers can obtain thumbnails of arbitrary files through the nativeImage APIEPSS 1.1%CVE-2022-29247LOWExposure of Resource to Wrong Sphere in ElectronEPSS 1.0%CVE-2020-4077HIGHContext isolation bypass via contextBridge in ElectronEPSS 1.0%CVE-2022-21718LOWRenderers can obtain access to random bluetooth device without permission in ElectronEPSS 0.9%

References