NVD / CVE Program· CNA GitHub_M

CVE-2026-70611: Electron: DevTools embedder handler executes arbitrary files via shell open

Noroxi assessment

Priority: Monitor (action score 27/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.18% (FIRST EPSS).
Someone with local access to the system can trigger it. Administrator privileges are required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
Fixed version: electron electron 39.8.9.

Low priority for now. Upgrade to electron electron 39.8.9 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 39.8.9, 40.9.2, 41.2.1, and 42.0.0-beta.3, the DevTools reveal in file manager action could launch the target file rather than reveal it. An attacker with a separate means of running script inside the DevTools frontend, such as a malicious DevTools extension, could use showItemInFolder handling to execute native code outside the sandbox when DevTools is opened for windows exposed to untrusted content or untrusted DevTools extensions. This issue is fixed in 39.8.9, 40.9.2, 41.2.1, and 42.0.0-beta.3.

MediumCVSS 6.9 · v3.1—No exploit Fix available

GHSA-f2r8-jv7c-xqmp

Published: Aug 5, 2026
Updated: Nov 3, 2026
EPSS: 0.1% · 8th percentile
CWE: CWE-78

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 27 / 40 · 6.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 6.9; NVD has not scored this yet; the score shown is the CNA’s.

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 39.8.9
electronjs electron40.0.0 and later · before 40.9.2
electronjs electron41.0.0 and later · before 41.2.1
electronjs electron42.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
- < 39.8.9, >= 40.0.0-alpha.1, < 40.9.2, >= 41.0.0-alpha.1, < 41.2.1, >= 42.0.0-alpha.1, < 42.0.0-beta.3affected

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 40.0.0-alpha.1 · before 40.9.2	40.9.2
npm	electron	from 41.0.0-alpha.1 · before 41.2.1	41.2.1
npm	electron	from 42.0.0-alpha.1 · before 42.0.0-beta.3	42.0.0-beta.3
npm	electron	before 39.8.9	39.8.9

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-70609Aug 5, 2026 · Electron: DevTools JavaScript Injection via Unsanitized Dock State Parameter
22Monitor
← EarlierCVE-2026-70610Aug 5, 2026 · Electron: contextBridge object copy honors prototype setters
21Monitor
Later →CVE-2026-70612Aug 5, 2026 · Electron: Sandboxed iframes can launch external protocol handlers
21Monitor

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
electron electron	39.8.9 · description	Vendor (CNA)
npm:electron	39.8.9	Package registry (OSV)
npm:electron	40.9.2	Package registry (OSV)
npm:electron	41.2.1	Package registry (OSV)
npm:electron	42.0.0-beta.3	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.

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-34779124 days apartElectron: AppleScript injection in app.moveToApplicationsFolder on macOS
31Monitor

Chain candidates

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

CVE-2026-34778124 days apartElectron: Service worker can spoof executeJavaScript IPC replies
26Monitor

Bug bounty scope

No known public program.

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

Technical details

Attack conditions

Someone with local access to the system can trigger it.
Administrator privileges are required.
A user must open a link or visit a page.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Local
Attack complexity: High
Privileges required: High
User interaction: Required
Scope: Changed
Confidentiality impact: High
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CVSS vector

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

nvd-secondary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

The bug in code

The whole CWE-78 class

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

Vulnerable

1const host = req.body.host;
2exec("ping -c 1 " + host, onResult);

Fixed

1const host = req.body.host;
2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
3execFile("ping", ["-c", "1", host], onResult);

Attack context

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

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

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

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

References

github.com/electron/electron/commit/10fb5b39c5287f70c4bbcab4c24197f3871ec322

Show all references (12 more)

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

All records