CVE-2026-34764

Workarounds

Ensure texture.release() is called promptly after the texture has been consumed, before the texture object becomes unreachable.

Fixed Versions

• 42.0.0-alpha.5
• 41.1.0
• 40.8.5
• 39.8.5

For more information

If there are any questions or comments about this advisory, send an email to [email protected]

Apps that use offscreen rendering with GPU shared textures may be vulnerable to a use-after-free. Under certain conditions, the release() callback provided on a paint event texture can outlive its backing native state, and invoking it after that point dereferences freed memory in the main process, which may lead to a crash or memory corruption.

Apps are only affected if they use offscreen rendering with webPreferences.offscreen: { useSharedTexture: true }. Apps that do not enable shared-texture offscreen rendering are not affected.

Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.

CVE-2026-34764 has a CVSS score of 2.3 (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.5, 40.8.5, 41.1.0, 42.0.0-alpha.5); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-34764? CVE-2026-34764 is a low-severity use after free vulnerability in electron (npm), affecting versions >= 33.0.0-alpha.1, < 39.8.5. It is fixed in 39.8.5, 40.8.5, 41.1.0, 42.0.0-alpha.5. Memory is accessed after it has been freed, leading to undefined behavior in native code.
2. How severe is CVE-2026-34764? CVE-2026-34764 has a CVSS score of 2.3 (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-34764? electron (npm) versions >= 33.0.0-alpha.1, < 39.8.5 is affected.
4. Is there a fix for CVE-2026-34764? Yes. CVE-2026-34764 is fixed in 39.8.5, 40.8.5, 41.1.0, 42.0.0-alpha.5. Upgrade to this version or later.
5. Is CVE-2026-34764 exploitable, and should I be worried? Whether CVE-2026-34764 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-34764 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-34764?
   • Upgrade electron to 39.8.5 or later
   • Upgrade electron to 40.8.5 or later
   • Upgrade electron to 41.1.0 or later
   • Upgrade electron to 42.0.0-alpha.5 or later