Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

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

CVE-2026-34771GHSA-8337-3p73-46f4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 41.0.0-beta.8, 40.7.0, 39.8.0, 38.8.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm electron

    Affected
    < 38.8.6>= 39.0.0-alpha.1, < 39.8.0>= 40.0.0-alpha.1, < 40.7.0>= 41.0.0-alpha.1, < 41.0.0-beta.8
    Fixed in
    41.0.0-beta.8, 39.8.0, 38.8.6, 40.7.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-34771: 0.29% estimated exploitation activity in the next 30 days; percentile 21.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-8337-3p73-46f4

  2. Revision 1 · created ·

    Published from osv record GHSA-8337-3p73-46f4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34771

Advisory: Electron: Use-after-free in WebContents fullscreen, pointer-lock, and keyboard-lock permission callbacks
IDs: CVE-2026-34771, GHSA-8337-3p73-46f4
Record: https://patchnext.com/advisories/cve-2026-34771 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 41.0.0-beta.8, 40.7.0, 39.8.0, 38.8.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected < 38.8.6; >= 39.0.0-alpha.1, < 39.8.0; >= 40.0.0-alpha.1, < 40.7.0; >= 41.0.0-alpha.1, < 41.0.0-beta.8; fixed in 41.0.0-beta.8, 39.8.0, 38.8.6, 40.7.0

## Suggested inspection (read-only)
- `npm ls electron --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8337-3p73-46f4 (OSV record GHSA-8337-3p73-46f4 lists affected ranges: npm electron >=0 =39.0.0-alpha.1 =40.0.0-alpha.1 =41.0.0-alpha.1 <41.0.0-beta.8 (fixed))
- Verified: https://github.com/advisories/GHSA-8337-3p73-46f4 (GitHub-reviewed advisory GHSA-8337-3p73-46f4 lists affected ranges: npm electron >=0 =39.0.0-alpha.1 =40.0.0-alpha.1 =41.0.0-alpha.1 <41.0.0-beta.8)

Commands are suggestions: review each one before running it.

Loading voting…