Electron up to 39.8.8/40.9.1/41.2.0/42.0.0-beta.2 DevTools showItemInFolder sandbox
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 1.78 |
Summary
A vulnerability was found in Electron up to 39.8.8/40.9.1/41.2.0/42.0.0-beta.2. It has been classified as critical. The impacted element is the function showItemInFolder of the component DevTools. Performing a manipulation results in sandbox.
This vulnerability is cataloged as CVE-2026-70611. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Electron up to 39.8.8/40.9.1/41.2.0/42.0.0-beta.2. It has been classified as critical. This affects the function showItemInFolder of the component DevTools. The manipulation with an unknown input leads to a sandbox vulnerability. CWE is classifying the issue as CWE-265. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-70611 since 08/04/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1611 for this issue.
Upgrading to version 39.8.9, 40.9.2, 41.2.1 or 42.0.0-beta.3 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 39.8.0
- 39.8.1
- 39.8.2
- 39.8.3
- 39.8.4
- 39.8.5
- 39.8.6
- 39.8.7
- 39.8.8
- 40.9.0
- 40.9.1
- 41.0
- 41.1
- 41.2.0
- 42.0.0-beta.0
- 42.0.0-beta.1
- 42.0.0-beta.2
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: SandboxCWE: CWE-265 / CWE-264
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Electron 39.8.9/40.9.2/41.2.1/42.0.0-beta.3
Timeline
08/04/2026 CVE reserved08/05/2026 Advisory disclosed
08/05/2026 VulDB entry created
08/05/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-70611 (🔒)
GCVE (CVE): GCVE-0-2026-70611
GCVE (VulDB): GCVE-100-386349
Entry
Created: 08/05/2026 20:30Changes: 08/05/2026 20:30 (55)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.