NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 35/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
Fixed version: electron (npm) 39.8.0, 40.7.0, 41.0.0-beta.8.

Low priority for now. Upgrade to electron (npm) 39.8.0, 40.7.0, 41.0.0-beta.8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Electron 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.

HighCVSS 8.8 · v3.1—No exploit Fix available

GHSA-8337-3p73-46f4

Published: Apr 3, 2026
Updated: Jul 24, 2026
EPSS: 0.3% · 30th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 8.8
CNA · GitHub_M: 7.5; 1.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
electronjs	electron	cpe:2.3:a:electronjs:electron

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

electronjs electronbefore 38.8.6
electronjs electron39.0.0 and later · before 39.8.0
electronjs electron40.0.0 and later · before 40.7.0
electronjs electron41.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

electron electron
- < 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.8affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
npm	electron	from 39.0.0-alpha.1 · before 39.8.0	39.8.0
npm	electron	from 40.0.0-alpha.1 · before 40.7.0	40.7.0
npm	electron	from 41.0.0-alpha.1 · before 41.0.0-beta.8	41.0.0-beta.8
npm	electron	before 38.8.6	38.8.6

Same product

electronjs: all records

Other highest-scoring records for the same primary product.

CVE-2017-16151Based on details posted by the ElectronJS team; A remote code execution vulnerability has been discovered in Google Chromium that affects al
40Plan
CVE-2026-102676Electron: <webview> can enable Node.js integration in Web Workers despite embedder restrictions
39Monitor
CVE-2026-34775Electron: nodeIntegrationInWorker not correctly scoped in shared renderer processes
39Monitor

Published before and after this one in the same product

← EarlierCVE-2026-34769Apr 3, 2026 · Electron: Renderer command-line switch injection via undocumented commandLineSwitches webPreference
35Monitor
← EarlierCVE-2026-34770Apr 3, 2026 · Electron: Use-after-free in PowerMonitor on Windows and macOS
35Monitor
Later →CVE-2026-34772Apr 3, 2026 · Electron: Use-after-free in download save dialog callback
35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
npm:electron	38.8.6	Package registry (OSV)
npm:electron	39.8.0	Package registry (OSV)
npm:electron	40.7.0	Package registry (OSV)
npm:electron	41.0.0-beta.8	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-347700 days apartElectron: Use-after-free in PowerMonitor on Windows and macOS
35Monitor
CVE-2026-347720 days apartElectron: Use-after-free in download save dialog callback
35Monitor
CVE-2026-347740 days apartElectron: Use-after-free in offscreen child window paint callback
32Monitor
CVE-2026-347643 days apartElectron has a use-after-free in offscreen shared texture release() callback
22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
A user must open a link or visit a page.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/electron/electron/security/advisories/GHSA-8337-3p73-46f4

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records