Skip to content

Electron: DevTools embedder handler executes arbitrary files via shell open

Moderate severity GitHub Reviewed Published Jul 27, 2026 in electron/electron • Updated Aug 5, 2026

Package

npm electron (npm)

Affected versions

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

Patched versions

39.8.9
40.9.2
41.2.1
42.0.0-beta.3

Description

Impact

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 this to execute native code outside the sandbox.

Apps are only affected if DevTools is opened for windows exposed to untrusted content or untrusted DevTools extensions. Apps that do not open DevTools in that context are not affected.

Workarounds

Do not open DevTools for windows that load untrusted content, and do not load untrusted DevTools extensions.

Fixed Versions

  • 42.0.0-beta.3
  • 41.2.1
  • 40.9.2
  • 39.8.9

For more information

If you have any questions or comments about this advisory, email Electron at security@electronjs.org

References

@MarshallOfSound MarshallOfSound published to electron/electron Jul 27, 2026
Published to the GitHub Advisory Database Aug 5, 2026
Reviewed Aug 5, 2026
Last updated Aug 5, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(3rd percentile)

Weaknesses

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Learn more on MITRE.

CVE ID

CVE-2026-70611

GHSA ID

GHSA-f2r8-jv7c-xqmp

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.