Electron vulnerable to ID collision when routing IPC messages to renderers containing OOPIFs
cve-program · CVE-2020-26272
PublishedThe 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.
Read the publisher's advisoryeuvd · EUVD-2021-0507
PublishedThe 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.
Read the publisher's advisorynvd · CVE-2020-26272
PublishedThe 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.
Read the publisher's advisoryosv · GHSA-hvf8-h2qh-37m9
Published### 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 [[email protected]](mailto:[email protected]).
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2020-26272
PublishedElectron vulnerable to ID collision when routing IPC messages to renderers containing OOPIFs
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.
- Source published
- 28 Jan 2021 18:25:17 UTC
- Source modified
- 27 May 2025 15:20:11 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
euvd · EUVD-2021-0507
PublishedThe 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 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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jan 28, 2021, 6:25:17 PM
dateUpdated: May 27, 2025, 3:20:11 PM
- Source published
- Jan 28, 2021, 6:25:17 PM (timezone not stated)
- Source modified
- May 27, 2025, 3:20:11 PM (timezone not stated)
- Saved here
- 17 Nov 2026 23:33:12 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
nvd · CVE-2020-26272
PublishedThe 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 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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-668
Original publisher date fields
published: 2021-01-28T19:15:13.003
lastModified: 2026-06-17T03:07:58.277
77 source CPE criteria · context only
- cpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta1:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta10:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta11:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta12:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta13:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta14:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta15:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta16:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta17:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta18:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta19:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta2:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta20:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta21:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta22:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta23:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta24:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta3:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta4:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta5:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta6:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta7:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta8:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:9.0.0:beta9:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta1:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta10:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta11:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta12:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta13:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta14:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta15:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta17:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta19:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta2:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta20:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta21:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta23:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta24:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta25:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta3:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta4:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta5:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta6:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta7:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta8:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:10.0.0:beta9:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta1:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta10:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta11:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta12:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta13:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta14:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta15:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta16:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta17:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta18:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta19:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta20:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta21:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta22:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta23:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta3:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta4:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta5:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta6:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta7:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta8:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:11.0.0:beta9:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:12.0.0:beta1:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:12.0.0:beta3:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:12.0.0:beta4:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:12.0.0:beta5:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:12.0.0:beta6:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:12.0.0:beta7:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:12.0.0:beta8:*:*:*:*:*:*
- cpe:2.3:a:electronjs:electron:12.0.0:beta9:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 28 Jan 2021 19:15:13 UTC
- Source modified
- 17 Jun 2026 03:07:58 UTC
- Saved here
- 24 Oct 2026 16:17:32 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
CVSS 3.1 · [email protected] · Primary · 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CVSS 2.0 · [email protected] · Primary · 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N
osv · GHSA-hvf8-h2qh-37m9
PublishedIPC messages delivered to the wrong frame in Electron
### 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 [[email protected]](mailto:[email protected]).
- Source published
- 28 Jan 2021 19:11:34 UTC
- Source modified
- 10 Sep 2026 03:49:13 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Publisher rating · MODERATE