CVE-2026-34770
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.1, 40.8.0, and 41.0.0-beta.8, apps that use the powerMonitor module may be vulnerable to a use-after-free. After the native PowerMonitor object is garbage-collected, the associated OS-level resources (a message window on Windows, a shutdown handler on macOS) retain dangling references. A subsequent session-change event (Windows) or system shutdown (macOS) dereferences freed memory, which may lead to a crash or memory corruption. All apps that access powerMonitor events (suspend, resume, lock-screen, etc.) are potentially affected. The issue is not directly renderer-controllable. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.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 confidenceElectron's powerMonitor module has a use-after-free vulnerability where OS-level resources (message window on Windows, shutdown handler on macOS) retain dangling references after the native PowerMonitor object is garbage-collected. Triggering session-change events or system shutdown after garbage collection dereferences freed memory, causing potential crashes 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.1>= 40.0.0, < 40.8.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.
-
Check the Electron versionInspect the Electron dependency version in your project's package.json file, or retrieve it programmatically in the main process using process.versions.electron or app.getVersion()Affected if The installed version is less than 38.8.6, or greater than or equal to 39.0.0 but less than 39.8.1, or greater than or equal to 40.0.0 but less than 40.8.0, or exactly 41.0.0
-
Identify powerMonitor usage in the codebaseSearch your application code for require('electron').powerMonitor or import { powerMonitor } from 'electron', or look for direct references to the powerMonitor module in your main process filesAffected if The powerMonitor module is imported or required in your application code
-
Check for event listeners on powerMonitorSearch for powerMonitor.on( method calls in your main process code, particularly looking for 'suspend', 'resume', 'lock-screen', or 'unlock-screen' event subscriptionsAffected if Your code attaches event listeners to powerMonitor for any of these events: suspend, resume, lock-screen, or unlock-screen
You are affected if your Electron version falls within the vulnerable ranges AND your application uses the powerMonitor module to listen to suspend, resume, lock-screen, or unlock-screen events.
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.140.8.0
Update Electron to version 38.8.6, 39.8.1, 40.8.0, or 41.0.0-beta.8 or later. Applications using powerMonitor events (suspend, resume, lock-screen) should be tested on both Windows and macOS after upgrading.
Upgrade to Electron 38.8.6 (for 38.x branch), 39.8.1 (for 39.x branch), 40.8.0 (for 40.x branch), or 41.0.0-beta.8/41.0.1+ (for 41.x branch) - choose the patched version matching your current major version
- Identify the current Electron version in your project by checking package.json or running npm list electron
- Determine which major version branch you're currently on (38.x, 39.x, 40.x, or 41.x)
- Update your package.json to specify the patched version for your branch: for 38.x use 38.8.6, for 39.x use 39.8.1, for 40.x use 40.8.0, or for 41.x use 41.0.0-beta.8 (or wait for stable 41.0.1+)
- Run npm install electron@<version> or yarn add electron@<version> to install the patched version
- Rebuild any native modules if your app uses them (run electron-rebuild if applicable)
- Test your application thoroughly, especially powerMonitor event handlers for suspend, resume, lock-screen, and session-change events
- Redeploy your application to users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34770 — 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-34770 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