CVE-2026-34772
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedElectron 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 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. This issue has been patched in versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUse-after-free vulnerability in Electron where destroying a session while a native save-file dialog is open for a download causes freed memory to be dereferenced when the dialog is dismissed, potentially leading to crash or memory corruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 38.8.6>= 39.0.0, < 39.8.0>= 40.0.0, < 40.7.0= 41.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Electron versionRun `electron --version` from the application directory, or check the version in package.json under dependencies or devDependencies. Also inspect the lock file (package-lock.json or yarn.lock) for the exact electron version resolved.Affected if The version is less than 38.8.6, or falls between 39.0.0 and 39.7.x, or falls between 40.0.0 and 40.6.x, or is exactly 41.0.0.
-
Determine if the application destroys sessions at runtimeSearch the codebase for calls to `session.fromPartition`, `partition.clearSessionData`, or any code path that calls `session.destroy()`. Review the main process code for dynamic session teardown logic.Affected if The application code contains logic that programmatically destroys or clears session objects while the app is running.
-
Verify if download functionality is enabledSearch the codebase for `download` event handlers on the webContents or session objects, or check for `will-download` event listeners. Also look for usage of `session.setDownloadPath` or `webContents.downloadURL`.Affected if The application has code that handles or initiates downloads, which enables the native save-file dialog to appear.
-
Inspect for crashes related to dialog dismissalReview application crash logs, error reports, or console output for use-after-free errors, memory corruption, or crashes occurring immediately after a save-file dialog is closed during an active download.Affected if Crashes or memory errors are logged when dismissing a save dialog during an active download session.
You are affected if your Electron version is within the vulnerable ranges AND your application destroys sessions at runtime AND downloads with save-file dialogs are possible in your app.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped38.8.639.8.040.7.0
Upgrade Electron to version 38.8.6, 39.8.0, 40.7.0, or 41.0.0-beta.8 or later. If upgrade is not immediately feasible, avoid programmatically destroying sessions while download dialogs are pending.
Upgrade to Electron 38.8.6, 39.8.0, 40.7.0, or any version >= 41.0.0-beta.8 (preferably the latest stable release)
- 1. Identify the current Electron version in use by checking package.json or node_modules/electron/package.json
- 2. If using Electron < 38.8.6, upgrade to version 38.8.6 or later
- 3. If using Electron >= 39.0.0 and < 39.8.0, upgrade to version 39.8.0 or later
- 4. If using Electron >= 40.0.0 and < 40.7.0, upgrade to version 40.7.0 or later
- 5. If using Electron 41.0.0, upgrade to version 41.0.0-beta.8 or later (or the stable 41.x release)
- 6. After upgrading, rebuild native modules with electron-rebuild if applicable
- 7. Test the application, particularly focusing on download functionality and session lifecycle management
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34772 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data