CVE-2026-70598

Electron: Off-screen rendering trusts GPU-supplied geometry over shared-memory size

Workarounds

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

Fixed Versions

• 42.0.0-beta.3
• 41.2.1
• 40.9.0
• 39.8.10

For more information

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

In offscreen rendering mode, frame data received from the GPU process was not fully validated by the main process. A compromised GPU process could cause the main process to read out-of-bounds memory while producing paint event images, disclosing memory or crashing the app.

Apps are only affected if they use offscreen rendering (webPreferences.offscreen) and an attacker has separately gained code execution in the GPU process. Apps that do not use offscreen rendering are not affected.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

CVE-2026-70598 has a CVSS score of 3.9 (Low). The vector is requires local access, high 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 (39.8.10, 40.9.0, 41.2.1, 42.0.0-beta.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-70598? CVE-2026-70598 is a low-severity out-of-bounds read vulnerability in electron (npm), affecting versions < 39.8.10. It is fixed in 39.8.10, 40.9.0, 41.2.1, 42.0.0-beta.3. A read operation accesses a memory location beyond the intended buffer boundary.
2. How severe is CVE-2026-70598? CVE-2026-70598 has a CVSS score of 3.9 (Low). 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-70598? electron (npm) versions < 39.8.10 is affected.
4. Is there a fix for CVE-2026-70598? Yes. CVE-2026-70598 is fixed in 39.8.10, 40.9.0, 41.2.1, 42.0.0-beta.3. Upgrade to this version or later.
5. Is CVE-2026-70598 exploitable, and should I be worried? Whether CVE-2026-70598 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-70598 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-70598?
   • Upgrade electron to 39.8.10 or later
   • Upgrade electron to 40.9.0 or later
   • Upgrade electron to 41.2.1 or later
   • Upgrade electron to 42.0.0-beta.3 or later

Other vulnerabilities in electron