Summary
Electron: File and HTTP protocol handlers allow cross-origin reads without corsEnabled
Workarounds
Set corsEnabled: true on the scheme, or do not load untrusted content in windows that can reach it.
Fixed Versions
44.0.0-beta.543.4.142.9.241.10.6
For more information
If you have any questions or comments about this advisory, email us at [email protected]
Impact
Responses served through protocol.registerFileProtocol or protocol.registerHttpProtocol for a custom scheme registered with supportFetchAPI: true but without corsEnabled: true could be read cross-origin by web content. This completes the fix for CVE-2026-70604.
Apps are only affected if they register such a scheme, serve it through one of those handlers, and load untrusted content. Apps that set corsEnabled: true, or that do not load untrusted content, are not affected.
CVE-2026-102675 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
electron to 41.10.6 or later; electron to 42.9.2 or later; electron to 43.4.1 or later; electron to 44.0.0-beta.5 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-102675? CVE-2026-102675 is a high-severity security vulnerability in electron (npm), affecting versions < 41.10.6. It is fixed in 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5.
- How severe is CVE-2026-102675? CVE-2026-102675 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of electron are affected by CVE-2026-102675? electron (npm) versions < 41.10.6 is affected.
- Is there a fix for CVE-2026-102675? Yes. CVE-2026-102675 is fixed in 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5. Upgrade to this version or later.
- Is CVE-2026-102675 exploitable, and should I be worried? Whether CVE-2026-102675 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-102675 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-102675?
- Upgrade
electronto 41.10.6 or later - Upgrade
electronto 42.9.2 or later - Upgrade
electronto 43.4.1 or later - Upgrade
electronto 44.0.0-beta.5 or later
- Upgrade