Electron: File and HTTP protocol handlers allow cross-origin reads without corsEnabled
electron
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
electron
| Product | Affected | Fixed in |
|---|---|---|
| electron npm |
|
|
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5, responses served through protocol.registerFileProtocol or protocol.registerHttpProtocol for a custom scheme registered with supportFetchAPI enabled but corsEnabled disabled could remain script-readable across origins. This residual issue completes the remediation for CVE-2026-70604. Applications are affected only when they expose such a scheme and load untrusted content in the same session. Schemes intentionally registered with corsEnabled enabled remain cross-origin readable by design. This issue is fixed in versions 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5.
From the CVE record · GitHub_M
Electron can leave responses from custom schemes script-readable across origins when the scheme uses protocol.registerFileProtocol or protocol.registerHttpProtocol with supportFetchAPI enabled and corsEnabled disabled. This affects applications that expose such a scheme and load untrusted content in the same session; the input does not specify authentication or user-interaction requirements.
Engineers using the npm electron package should check versions below 41.10.6, 42.0.0-alpha.1 through versions below 42.9.2, 43.0.0-alpha.1 through versions below 43.4.1, and 44.0.0-alpha.1 through versions below 44.0.0-beta.5.