Summary
Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions
Workarounds
Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content.
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
Windows opened from a sandboxed top-level document did not inherit that document's HTML sandbox restrictions, so content that was meant to run sandboxed could open a window with the app's full origin. GHSA-hq2x-r82h-9wj4 covers the same issue for sandboxed iframes.
Apps are only affected if they render untrusted content in a sandboxed top-level document that allows popups. Apps that deny popups from untrusted content with setWindowOpenHandler are not affected.
CVE-2026-102674 has a CVSS score of 8.2 (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-102674? CVE-2026-102674 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-102674? CVE-2026-102674 has a CVSS score of 8.2 (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-102674? electron (npm) versions < 41.10.6 is affected.
- Is there a fix for CVE-2026-102674? Yes. CVE-2026-102674 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-102674 exploitable, and should I be worried? Whether CVE-2026-102674 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-102674 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-102674?
- 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