Summary
Electron: Local race condition in Squirrel.Mac update installation on macOS
Workarounds
There are no app side workarounds, you must update to a patched version of Electron.
Fixed Versions
42.0.0-beta.241.10.539.8.10
For more information
If you have any questions or comments about this advisory, email us at [email protected]
Impact
On macOS, Electron bundles the Squirrel.Mac auto-update framework, whose privileged ShipIt helper performs the final step of an update as root. A local attacker could cause that helper to overwrite a different application's files, as root, instead of the app that started the update. Exploitation requires local access to the machine.
Apps are only affected on macOS if they ship Squirrel.Mac-based auto-updates. Apps on other platforms, or that do not use Squirrel.Mac auto-updates, are not affected.
CVE-2026-102672 has a CVSS score of 6.7 (Medium). The vector is requires local access, low 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 (39.8.10, 41.10.5, 42.0.0-beta.2); 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 39.8.10 or later; electron to 41.10.5 or later; electron to 42.0.0-beta.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-102672? CVE-2026-102672 is a medium-severity security vulnerability in electron (npm), affecting versions < 39.8.10. It is fixed in 39.8.10, 41.10.5, 42.0.0-beta.2.
- How severe is CVE-2026-102672? CVE-2026-102672 has a CVSS score of 6.7 (Medium). 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-102672? electron (npm) versions < 39.8.10 is affected.
- Is there a fix for CVE-2026-102672? Yes. CVE-2026-102672 is fixed in 39.8.10, 41.10.5, 42.0.0-beta.2. Upgrade to this version or later.
- Is CVE-2026-102672 exploitable, and should I be worried? Whether CVE-2026-102672 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-102672 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-102672?
- Upgrade
electronto 39.8.10 or later - Upgrade
electronto 41.10.5 or later - Upgrade
electronto 42.0.0-beta.2 or later
- Upgrade