CVE-2026-34771
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 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.
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 versions prior to 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8 contain a use-after-free vulnerability in the async session.setPermissionRequestHandler() for fullscreen, pointer-lock, and keyboard-lock permissions. If the requesting frame navigates or the window closes while the permission handler is pending, the stored callback dereferences freed memory, causing potential crash or memory corruption. Apps using synchronous handlers or no custom handler are unaffected.
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.
-
Check installed Electron versionRun 'electron --version' in the application environment, or inspect the version field in package.json under dependencies or devDependenciesAffected if The version is less than 38.8.6, or >= 39.0.0 and < 39.8.0, or >= 40.0.0 and < 40.7.0, or equals 41.0.0 (not a beta)
-
Locate setPermissionRequestHandler usageSearch source code files (JavaScript, TypeScript) for the string 'setPermissionRequestHandler' using grep or IDE searchAffected if The application code contains a call to session.setPermissionRequestHandler()
-
Identify permission types handledExamine the handler callback registered with setPermissionRequestHandler and identify which permission strings are handled (fullscreen, pointer-lock, keyboard-lock)Affected if The handler processes fullscreen, pointer-lock, or keyboard-lock permissions
-
Determine if handlers are asynchronousReview the handler callback implementation to see if it returns a Promise, uses async/await, or calls asynchronous APIs before resolving the permission requestAffected if The handler for fullscreen, pointer-lock, or keyboard-lock performs async operations or returns a Promise rather than resolving synchronously
-
Check for concurrent navigation or window close logicSearch for code that performs window navigation (loadURL, loadFile, navigate) or window.close() and assess whether it can execute while a permission handler is pendingAffected if The application can navigate away from the current page or close the window while a permission request is awaiting a response
You are affected if your Electron version falls within the vulnerable ranges AND your application uses async handlers with setPermissionRequestHandler for fullscreen, pointer-lock, or keyboard-lock permissions where navigation or window close can occur while the handler is pending.
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. Alternatively, convert async permission handlers to respond synchronously if upgrading is not immediately feasible.
Upgrade to Electron 38.8.6, 39.8.0, 40.7.0, or 41.0.0-beta.8 (depending on your current major version branch)
- 1. Identify the current Electron version in your project by checking package.json or the electron package version
- 2. Determine which version branch you are on (38.x, 39.x, 40.x, or 41.x)
- 3. Update the electron dependency in package.json to the appropriate fixed version for your branch: 38.8.6 for 38.x, 39.8.0 for 39.x, 40.7.0 for 40.x, or 41.0.0-beta.8 for 41.x
- 4. Run npm install or yarn install to update the dependency
- 5. Rebuild and test your application to verify the fix resolves the use-after-free vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34771 — 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-34771 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