CVE-2026-34771: Electron: Use-after-free in WebContents fullscreen, pointer-lock, and keyboard-lock permission callbacks

Published Apr 3, 2026
·
Updated

Impact Apps that register an asynchronous session.setPermissionRequestHandler() may be vulnerable to a use-after-free when handling fullscreen, pointer-lock, or keyboard-lock permission requests. If the requesting frame navigates or the window closes while the permission handler is pending, invoking the stored callback dereferences freed memory, which may lead to a crash or memory corruption.

Apps that do not set a permission request handler, or whose handler responds synchronously, are not affected.

Workarounds Respond to permission requests synchronously, or deny fullscreen, pointer-lock, and keyboard-lock requests if an asynchronous flow is required.

Fixed Versions 41.0.0-beta.8 40.7.0 39.8.0 38.8.6

For more information If there are any questions or comments about this advisory, please email security@electronjs.org

Other sources

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8, apps that register an asynchronous session.setPermissionRequestHandler() may be vulnerable to a use-after-free when handling fullscreen, pointer-lock, or keyboard-lock permission requests. If the requesting frame navigates or the window closes while the permission handler is pending, invoking the stored callback dereferences freed memory, which may lead to a crash or memory corruption. Apps that do not set a permission request handler, or whose handler responds synchronously, are not affected. This issue has been patched in versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8.

MITRE

Affected Software

20 affected componentsFixes available
npm/electron>=41.0.0-alpha.1<41.0.0-beta.8
41.0.0-beta.8
npm/electron>=40.0.0-alpha.1<40.7.0
40.7.0
npm/electron>=39.0.0-alpha.1<39.8.0
39.8.0
npm/electron<38.8.6
38.8.6
electronjs Electron Node.js<38.8.6
electronjs Electron Node.js>=39.0.0<39.8.0
electronjs Electron Node.js>=40.0.0<40.7.0
electronjs Electron Node.js=41.0.0-alpha1
electronjs Electron Node.js=41.0.0-alpha2
electronjs Electron Node.js=41.0.0-alpha3
electronjs Electron Node.js=41.0.0-alpha4
electronjs Electron Node.js=41.0.0-alpha5
electronjs Electron Node.js=41.0.0-alpha6
electronjs Electron Node.js=41.0.0-beta1
electronjs Electron Node.js=41.0.0-beta2
electronjs Electron Node.js=41.0.0-beta3
electronjs Electron Node.js=41.0.0-beta4
electronjs Electron Node.js=41.0.0-beta5
electronjs Electron Node.js=41.0.0-beta6
electronjs Electron Node.js=41.0.0-beta7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 41.0.0-beta.8
  2. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 40.7.0
  3. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 39.8.0
  4. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 38.8.6
  5. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 38.8.6
  6. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 39.8.0
  7. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 40.7.0
  8. Upgrade

    Upgrade Electron to a version that resolves this vulnerability.

    Fixed in 41.0.0-beta.8
  9. Configuration

    Update the app’s permission handling so permission requests are handled synchronously; alternatively, if an asynchronous flow is required, deny fullscreen, pointer-lock, and keyboard-lock permission requests to avoid the use-after-free in the stored callback.

    Electron (session.setPermissionRequestHandler) session.setPermissionRequestHandler callback handling = synchronous (or deny fullscreen/pointer-lock/keyboard-lock when using asynchronous flow)

Event History

Apr 3, 2026
Advisory Published
via GitHub·02:40 AM
Data Sourced
via GitHub·02:40 AM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·11:47 PM
Data Sourced
via MITRE·11:47 PM
DescriptionSeverityWeakness
Apr 4, 2026
Data Sourced
via Red Hat·12:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeaknessAffected 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