CVE-2026-70604

highpriority · track · 0EPSS 0.004 · 29 %ileEUUS

grimoire priorityP2 · Scheduled

Exploitable?

—

no known exploitation

Likely / severe?

0.35% (29th) EPSS

CVSS 7.4 · high

Is it mine?

12 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-27

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.10, 40.9.3, 41.4.0, and 42.0.0, a custom scheme registered with supportFetchAPI: true but without corsEnabled: true was not subject to CORS enforcement. A page loaded from a remote origin could therefore fetch() or XMLHttpRequest that scheme cross-origin and read the full response body, rather than the read being blocked. Apps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. This issue is fixed in versions 39.8.10, 40.9.3, 41.4.0, and 42.0.0.

cvss

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

7.4

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.8–7.4

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

v3.17.4highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:Nsecondary · security-advisories@github.comexploitability 2.8 · impact 4

v3.17.4highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:Nsecondary · OSV

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

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-942USCWE-942US

affected products (12)

Products and version ranges known to be affected.

Electron Electron≤ < 39.8.10enisa_euvdEU
Electron Electron40.0.0-alpha.1, → 40.9.3enisa_euvdEU
Electron Electron41.0.0-alpha.1, → 41.4.0enisa_euvdEU
Electron Electron42.0.0-alpha.1, → 42.0.0enisa_euvdEU
electronjs electron< 39.8.10nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron40.0.0 → 40.9.3nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron41.0.0 → 41.4.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron= 42.0.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
npm electron< 39.8.10osvUSpkg:npm/electron
npm electron40.0.0-alpha.1 → 40.9.3osvUSpkg:npm/electron
npm electron41.0.0-alpha.1 → 41.4.0osvUSpkg:npm/electron
npm electron42.0.0-alpha.1 → 42.0.0osvUSpkg:npm/electron

advisories (1)

Vendor and ecosystem advisories describing this.

GHSA-v3j7-r9gq-3gjwElectron: Custom protocol with supportFetchAPI but not corsEnabled allows cross-origin reads2026-08-05ghsa · osvUS
### Impact A custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked. Apps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected. ### Workarounds Set `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data. ### Fixed Versions * `42.0.0` * `41.4.0` * `40.9.3` * `39.8.10` ### For more information If you have any questions or comments about this advisory, email Electron 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 2026-08-05modified 2026-08-05

references (4)

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