CVE-2020-26272

mediumpriority · track · 27EPSS 0.017 · 78 %ileEUUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

1.75% (78th) EPSS

CVSS 6.4 · medium

Is it mine?

13 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-27

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

Technical severity, 0–10. One row per scoring source.

6.5

010

base score 0–10 · higher = more severe · hover a vector to decode

v2.06.4mediumAV:N/AC:L/Au:N/C:P/I:P/A:Nprimary · NVD / NIST USexploitability 10 · impact 4.9

v3.16.5mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Nprimary · NVD / NIST USexploitability 3.9 · impact 2.5

v3.15.4mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:Nsecondary · ENISA EU

v3.15.4mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:Nsecondary · security-advisories@github.comexploitability 2.2 · impact 2.7

v3.15.4mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:Nsecondary · OSV

v3.16mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:Usecondary · CVSS-BT (t0sche)

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-668USCWE-668US

affected products (13)

Products and version ranges known to be affected.

Electron Electron≤ < 9.4.0enisa_euvdEU
Electron Electron10.0.0, → 10.2.0enisa_euvdEU
Electron Electron11.0.0, → 11.1.0enisa_euvdEU
electronjs electron= 10.0.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron10.0.0 → 10.2.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron= 11.0.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron11.0.0 → 11.1.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron= 12.0.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron= 9.0.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron9.0.0 → 9.4.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
npm electron< 9.4.0osvUSpkg:npm/electron
npm electron10.0.0 → 10.2.0osvUSpkg:npm/electron
npm electron11.0.0 → 11.1.0osvUSpkg:npm/electron

advisories (1)

Vendor and ecosystem advisories describing this.

GHSA-hvf8-h2qh-37m9IPC messages delivered to the wrong frame in Electron2021-01-28ghsa · osvUS
### 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](mailto:security@electronjs.org).

also known as (3)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd nvd osv NVD CVE.org MITRE

published 2021-01-28modified 2026-06-17

references (29)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan