cve.bz

CVE-2026-70611 electronjs electron: OS Command Injection

6.9 mediumEPSS 0.2%Fix available

Medium (6.9) in electronjs electron. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in electron 39.8.9, 40.9.2, 41.2.1.

On this page
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.

Severity

CVSS 3.1

6.9 medium
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-08-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-70611 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-70611?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-70611?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-70611 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
electronjs:electronbefore 39.8.9
electronjs:electronfrom 40.0.0 before 40.9.2
electronjs:electronfrom 41.0.0 before 41.2.1
electronjs:electron42.0.0:alpha1
electronjs:electron42.0.0:alpha2
electronjs:electron42.0.0:alpha3
electronjs:electron42.0.0:alpha4
electronjs:electron42.0.0:alpha5
electronjs:electron42.0.0:alpha6
electronjs:electron42.0.0:beta1
electronjs:electron42.0.0:beta2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f2r8-jv7c-xqmpnpmelectron<39.8.939.8.9
GHSA-f2r8-jv7c-xqmpnpmelectron>=40.0.0-alpha.1 <40.9.240.9.2
GHSA-f2r8-jv7c-xqmpnpmelectron>=41.0.0-alpha.1 <41.2.141.2.1
GHSA-f2r8-jv7c-xqmpnpmelectron>=42.0.0-alpha.1 <42.0.0-beta.342.0.0-beta.3

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON