Electron: File and HTTP protocol handlers allow cross-origin reads without corsEnabled
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- electron electron
fixed in 41.10.6; From 42.0.0-alpha.1 · fixed in 42.9.2; From 43.0.0-alpha.1 · fixed in 43.4.1; From 44.0.0-alpha.1 · fixed in 44.0.0-beta.5
- electronnpm
fixed in 41.10.6
- electronnpm
From 42.0.0-alpha.1 · fixed in 42.9.2
- electronnpm
From 43.0.0-alpha.1 · fixed in 43.4.1
- electronnpm
From 44.0.0-alpha.1 · fixed in 44.0.0-beta.5