CVE-2026-34764: Electron has a use-after-free in offscreen shared texture release() callback

Published Apr 3, 2026
·
Updated

Impact 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.

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 security@electronjs.org

Other sources

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From 33.0.0-alpha.1 to before 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5, 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. To mitigate this issue, ensure texture.release() is called promptly after the texture has been consumed, before the texture object becomes unreachable. This vulnerability is fixed in 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5.

MITRE

Affected Software

11 affected componentsFixes available
npm/electron>=42.0.0-alpha.1<42.0.0-alpha.5
42.0.0-alpha.5
npm/electron>=41.0.0-alpha.1<41.1.0
41.1.0
npm/electron>=40.0.0-alpha.1<40.8.5
40.8.5
npm/electron>=33.0.0-alpha.1<39.8.5
39.8.5
electronjs Electron Node.js>=33.0.0<39.8.5
electronjs Electron Node.js>=40.0.0<40.8.5
electronjs Electron Node.js>=41.0.0<41.1.0
electronjs Electron Node.js=42.0.0-alpha1
electronjs Electron Node.js=42.0.0-alpha2
electronjs Electron Node.js=42.0.0-alpha3
electronjs Electron Node.js=42.0.0-alpha4

Event History

Apr 3, 2026
Advisory Published
via GitHub·09:52 PM
Data Sourced
via GitHub·09:52 PM
DescriptionSeverityWeaknessAffected Software
Apr 6, 2026
CVE Published
via MITRE·03:46 PM
Data Sourced
via MITRE·03:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
Affected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203