Electronjs Electron 11.0.0 Beta 9
Approved changes feed: RSS · Atom
cpe:2.3:a:electronjs:electron:11.0.0:beta9:*:*:*:*:*:*
part: a version: 11.0.0 update: beta9
| Vendor | Electronjs (2af93ff4-38f6-5aef-acc5-80ca92aa0b83) |
|---|---|
| Product | Electron (3ffe6bdf-afda-502c-ac98-8ec4a42261cc) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/electron/electron |
purl2cpe | 2026-06-01 10:17:08.311592 |
pkg:gitlab/immersaview/electron |
purl2cpe | 2026-06-01 10:17:08.311593 |
pkg:npm/electron |
purl2cpe | 2026-06-01 10:17:08.311594 |
pkg:sourceforge/electron.mirror |
purl2cpe | 2026-06-01 10:17:08.311596 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-26272 |
vulnerable | 2026-06-08 05:23:51.099133 |
Electron vulnerable to ID collision when routing IPC messages to renderers containing OOPIFs
MEDIUM (5.4)
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.
Published: 2021-01-28T18:25:17.000Z
Updated: 2025-05-27T15:20:11.927Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.