Electron: Use-after-free in download save dialog callback

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.8 · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:L

EPSS

• CVE-2026-34772: 0.21% estimated exploitation activity in the next 30 days; percentile 11.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Apps that allow downloads and programmatically destroy sessions may be vulnerable to a use-after-free. If a session is torn down while a native save-file dialog is open for a download, dismissing the dialog dereferences freed memory, which may lead to a crash or memory corruption. Apps that do not destroy sessions at runtime, or that do not permit downloads, are not affected. Workarounds Avoid destroying sessions while a download save dialog may be open. Cancel pending downloads before session teardown. Fixed Versions 41.0.0-beta.7 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

Published by the source

3 Apr 2026, 02:41 UTC

Last modified by the source

6 Apr 2026, 23:19 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9w97-2464-8783

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9w97-2464-8783

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

# Patch Next advisory brief: CVE-2026-34772

Advisory: Electron: Use-after-free in download save dialog callback
IDs: CVE-2026-34772, GHSA-9w97-2464-8783
Record: https://patchnext.com/advisories/cve-2026-34772 (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: Medium (CVSS 5.8)
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.7, 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.7; fixed in 41.0.0-beta.7, 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-9w97-2464-8783 (OSV record GHSA-9w97-2464-8783 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.7 (fixed))
- Verified: https://github.com/advisories/GHSA-9w97-2464-8783 (GitHub-reviewed advisory GHSA-9w97-2464-8783 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.7)

Commands are suggestions: review each one before running it.