CVE-2020-26272: Electron vulnerable to ID collision when routing IPC messages to renderers containing OOPIFs

Published Jan 28, 2021
·
Updated

Impact IPC 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 does ANY of the following, then it is impacted by this issue: - Uses remote - Calls webContents.sendToFrame - Calls event.reply in an IPC message handler

Patches This has been fixed in the following versions:

- 9.4.0 - 10.2.0 - 11.1.0 - 12.0.0-beta.9

Workarounds There are no workarounds for this issue.

For more information If you have any questions or comments about this advisory, email us at security@electronjs.org.

Other sources

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.

MITRE

The Electron framework lets you write cross-platform desktop applications using JavaScript, HTML and CSS. In affected versions of Electron IPC 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 workarounds for this issue.

Affected Software

82 affected componentsFixes available
electronjs Electron>=9.0.0<9.4.0
electronjs Electron>=10.0.0<10.2.0
electronjs Electron>=11.0.0<11.1.0
electronjs Electron=9.0.0-beta1
electronjs Electron=9.0.0-beta10
electronjs Electron=9.0.0-beta11
electronjs Electron=9.0.0-beta12
electronjs Electron=9.0.0-beta13
electronjs Electron=9.0.0-beta14
electronjs Electron=9.0.0-beta15
electronjs Electron=9.0.0-beta16
electronjs Electron=9.0.0-beta17
electronjs Electron=9.0.0-beta18
electronjs Electron=9.0.0-beta19
electronjs Electron=9.0.0-beta2
electronjs Electron=9.0.0-beta20
electronjs Electron=9.0.0-beta21
electronjs Electron=9.0.0-beta22
electronjs Electron=9.0.0-beta23
electronjs Electron=9.0.0-beta24
electronjs Electron=9.0.0-beta3
electronjs Electron=9.0.0-beta4
electronjs Electron=9.0.0-beta5
electronjs Electron=9.0.0-beta6
electronjs Electron=9.0.0-beta7
electronjs Electron=9.0.0-beta8
electronjs Electron=9.0.0-beta9
electronjs Electron=10.0.0-beta1
electronjs Electron=10.0.0-beta10
electronjs Electron=10.0.0-beta11
electronjs Electron=10.0.0-beta12
electronjs Electron=10.0.0-beta13
electronjs Electron=10.0.0-beta14
electronjs Electron=10.0.0-beta15
electronjs Electron=10.0.0-beta17
electronjs Electron=10.0.0-beta19
electronjs Electron=10.0.0-beta2
electronjs Electron=10.0.0-beta20
electronjs Electron=10.0.0-beta21
electronjs Electron=10.0.0-beta23
electronjs Electron=10.0.0-beta24
electronjs Electron=10.0.0-beta25
electronjs Electron=10.0.0-beta3
electronjs Electron=10.0.0-beta4
electronjs Electron=10.0.0-beta5
electronjs Electron=10.0.0-beta6
electronjs Electron=10.0.0-beta7
electronjs Electron=10.0.0-beta8
electronjs Electron=10.0.0-beta9
electronjs Electron=11.0.0-beta1
electronjs Electron=11.0.0-beta10
electronjs Electron=11.0.0-beta11
electronjs Electron=11.0.0-beta12
electronjs Electron=11.0.0-beta13
electronjs Electron=11.0.0-beta14
electronjs Electron=11.0.0-beta15
electronjs Electron=11.0.0-beta16
electronjs Electron=11.0.0-beta17
electronjs Electron=11.0.0-beta18
electronjs Electron=11.0.0-beta19
electronjs Electron=11.0.0-beta20
electronjs Electron=11.0.0-beta21
electronjs Electron=11.0.0-beta22
electronjs Electron=11.0.0-beta23
electronjs Electron=11.0.0-beta3
electronjs Electron=11.0.0-beta4
electronjs Electron=11.0.0-beta5
electronjs Electron=11.0.0-beta6
electronjs Electron=11.0.0-beta7
electronjs Electron=11.0.0-beta8
electronjs Electron=11.0.0-beta9
electronjs Electron=12.0.0-beta1
electronjs Electron=12.0.0-beta3
electronjs Electron=12.0.0-beta4
electronjs Electron=12.0.0-beta5
electronjs Electron=12.0.0-beta6
electronjs Electron=12.0.0-beta7
electronjs Electron=12.0.0-beta8
electronjs Electron=12.0.0-beta9
npm/electron>=11.0.0<11.1.0
11.1.0
npm/electron>=10.0.0<10.2.0
10.2.0
npm/electron<9.4.0
9.4.0

Event History

Jan 28, 2021
CVE Published
via MITRE·06:25 PM
Data Sourced
via MITRE·06:25 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·07:11 PM
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2020-26272?

CVE-2020-26272 has been assigned a medium severity rating.

2

How do I fix CVE-2020-26272?

To fix CVE-2020-26272, update Electron to version 9.4.0 or later.

3

Which versions are affected by CVE-2020-26272?

CVE-2020-26272 affects Electron versions from 9.0.0 to 11.1.0, including specific beta versions.

4

What type of vulnerability is CVE-2020-26272?

CVE-2020-26272 is an inter-process communication (IPC) vulnerability in Electron.

5

Does CVE-2020-26272 affect all Electron applications?

CVE-2020-26272 may affect any Electron application that utilizes the IPC messaging features between the main process and renderer process.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203