Electron up to 38.8.5/39.8.0/40.7.x on Windows Setting unquoted search path
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Electron up to 38.8.5/39.8.0/40.7.x on Windows. This issue affects some unknown processing of the component Setting Handler. The manipulation results in unquoted search path. This vulnerability is known as CVE-2026-34768. Attacking locally is a requirement. No exploit is available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in Electron up to 38.8.5/39.8.0/40.7.x on Windows. Affected is an unknown part of the component Setting Handler. The manipulation with an unknown input leads to a unquoted search path vulnerability. CWE is classifying the issue as CWE-428. The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8, on Windows, app.setLoginItemSettings({openAtLogin: true}) wrote the executable path to the Run registry key without quoting. If the app is installed to a path containing spaces, an attacker with write access to an ancestor directory may be able to cause a different executable to run at login instead of the intended app. On a default Windows install, standard system directories are protected against writes by standard users, so exploitation typically requires a non-standard install location. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-34768 since 03/30/2026. The exploitability is told to be difficult. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1574.009.
Upgrading to version 38.8.6, 39.8.1, 40.8.0 or 41.0.0-beta.8 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
- 38.8.0
- 38.8.1
- 38.8.2
- 38.8.3
- 38.8.4
- 38.8.5
- 39.0
- 39.1
- 39.2
- 39.3
- 39.4
- 39.5
- 39.6
- 39.7
- 39.8.0
- 40.0
- 40.1
- 40.2
- 40.3
- 40.4
- 40.5
- 40.6
- 40.7
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.5
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.9
CNA Vector (GitHub_M): 🔒
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: Unquoted search pathCWE: CWE-428 / CWE-426
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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 38.8.6/39.8.1/40.8.0/41.0.0-beta.8
Timeline
03/30/2026 CVE reserved04/04/2026 Advisory disclosed
04/04/2026 VulDB entry created
04/04/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-jfqx-fxh3-c62j
Status: Confirmed
CVE: CVE-2026-34768 (🔒)
GCVE (CVE): GCVE-0-2026-34768
GCVE (VulDB): GCVE-100-355260
Entry
Created: 04/04/2026 08:01Changes: 04/04/2026 08:01 (65)
Complete: 🔍
Cache ID: 216:1DA:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.