Metrics
Affected Vendors & Products
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-v3j7-r9gq-3gjw | Electron: Custom protocol with supportFetchAPI but not corsEnabled allows cross-origin reads |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 08 Oct 2026 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Electronjs
Electronjs electron |
|
| CPEs | cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:alpha1:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:alpha2:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:alpha3:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:alpha4:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:alpha5:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:alpha6:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:beta1:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:beta2:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:beta3:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:beta4:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:beta5:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:beta6:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:beta7:*:*:*:node.js:*:* cpe:2.3:a:electronjs:electron:42.0.0:beta8:*:*:*:node.js:*:* |
|
| Vendors & Products |
Electronjs
Electronjs electron |
Wed, 05 Aug 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 05 Aug 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Electron
Electron electron |
|
| Vendors & Products |
Electron
Electron electron |
Wed, 05 Aug 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Electron: Custom protocol with supportFetchAPI but not corsEnabled allows cross-origin reads | |
| Weaknesses | CWE-942 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-05T18:41:32.481Z
Reserved: 2026-08-04T19:50:27.328Z
Link: CVE-2026-70604
Updated: 2026-08-05T18:13:53.489Z
Status : Analyzed
Published: 2026-08-05T16:17:04.617
Modified: 2026-10-08T13:53:51.593
Link: CVE-2026-70604
No data.
OpenCVE Enrichment
Updated: 2026-08-05T18:15:05Z
Github GHSA