CVE-2026-102677

Electron: Sandboxed preload code cache can be poisoned by a compromised renderer

Workarounds

There are no app side workarounds, you must update to a patched version of Electron.

Fixed Versions

• 44.0.0-beta.6
• 43.5.0
• 42.10.0

For more information

If you have any questions or comments about this advisory, email us at [email protected]

The cache Electron keeps for sandboxed preload scripts did not verify that a cached entry matched the preload it was served for. A compromised renderer could use this to run its own code in the preload context on a later load.

Apps are only affected if they load untrusted content. Apps that do not load untrusted content are not affected.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2026-102677 has a CVSS score of 7.8 (High). The vector is requires local access, low privileges required, and no user interaction. 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 (42.10.0, 43.5.0, 44.0.0-beta.6); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-102677? CVE-2026-102677 is a high-severity improper input validation vulnerability in electron (npm), affecting versions >= 42.3.3, < 42.10.0. It is fixed in 42.10.0, 43.5.0, 44.0.0-beta.6. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2026-102677? CVE-2026-102677 has a CVSS score of 7.8 (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.
3. Which versions of electron are affected by CVE-2026-102677? electron (npm) versions >= 42.3.3, < 42.10.0 is affected.
4. Is there a fix for CVE-2026-102677? Yes. CVE-2026-102677 is fixed in 42.10.0, 43.5.0, 44.0.0-beta.6. Upgrade to this version or later.
5. Is CVE-2026-102677 exploitable, and should I be worried? Whether CVE-2026-102677 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
6. What actually determines whether CVE-2026-102677 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.
7. How do I fix CVE-2026-102677?
   • Upgrade electron to 42.10.0 or later
   • Upgrade electron to 43.5.0 or later
   • Upgrade electron to 44.0.0-beta.6 or later

Other vulnerabilities in electron