Microsoft
CVE-2026-34768
HIGH
Vulnerability Assessment
| Weakness | |
| Impact | The CVSS v3.1 score of 3.9 (Low) reflects the constrained attack vector and prerequisites. The vector AV:L (Local), AC:H (High Complexity), PR:H (High Privilege required), and UI:N indicates this requires local system access and high-privilege credentials, significantly limiting real-world exploitability. The EPSS score is not provided, but the low CVSS and multiple preconditions suggest limited practical exploitation probability. Notably, the vulnerability requires the application to be installed in a non-standard location with spaces in the path, AND ancestor directories must be writable by the attacker-conditions that contradict default Windows security posture where standard system directories (Program Files, ProgramData) are write-protected for standard users. This is a privilege-escalation vector for unprivileged users on misconfigured systems, not a broad-reach vulnerability. The presence of a fix across four release branches indicates vendor acknowledgment, but the narrow exploit window and non-default preconditions reduce this from a critical priority to a situational fix. |
| Exploit ScenarioDerived | An attacker with local access to a Windows system where an Electron application is installed to a path containing spaces (e.g., 'C:\Custom Install Folder\My App\app.exe') and the 'C:\Custom Install Folder' directory is world-writable discovers this misconfiguration. The attacker places a malicious executable named 'My.exe' in the Custom Install Folder directory. When the user logs in, Windows reads the unquoted registry entry 'C:\Custom Install Folder\My App\app.exe', parses it as 'C:\Custom Install Folder\My.exe' (truncating at the space), and executes the attacker's payload instead of the legitimate application. No public exploit code is identified at the time of analysis; exploitation requires local system access and favorable but non-default configuration conditions. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 03, 2026
Electron's setLoginItemSettings() function on Windows fails to quote executable paths in the Run registry key, allowing local attackers with write access to ancestor directories to execute arbitrary programs at login if the app is installed to a path containing spaces. The vulnerability affects Electron versions prior to 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8, and requires high-privilege access and unfavorable conditions (non-standard install paths) to exploit, making real-world impact limited to non-default Windows configurations.
RemediationAI
Update Electron to version 38.8.6 or later (for the 38.x series), 39.8.1 or later (39.x series), 40.8.0 or later (40.x series), or 41.0.0-beta.8 or later (41.x series). Application developers should regenerate and redeploy their Electron-based applications with the patched framework. As an interim workaround pending updates, end-users and system administrators should install affected applications to Windows paths without spaces (e.g., 'C:\Apps\MyApp' rather than 'C:\Program Files\My App'), or ensure all ancestor directories in the installation path are protected against unauthorized writes. Refer to the GitHub Security Advisory at https://github.com/electron/electron/security/advisories/GHSA-jfqx-fxh3-c62j for additional context and to verify patch availability for your specific Electron version.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Electron is a framework for building cross-platform desktop applications using web technologies. The setLoginItemSettings() API on Windows writes application paths to the Windows Registry's Run key to enable auto-launch at user login. The vulnerability stems from improper path handling: when an executable path contains spaces and is not quoted in the registry, the Windows registry parser interprets the path up to the first space as the executable to launch, with the remainder treated as arguments. If a directory in the path hierarchy (e.g., 'C:\Program Files (x86)\Company Name\App Name\app.exe') is writable by a non-administrative user, an attacker can place a malicious executable in an ancestor directory (e.g., 'C:\Program Files (x86)\Company Name\malicious.exe') to be executed instead. CWE-428 (Unquoted Search Path or Element) identifies the root cause: failure to properly quote or escape path elements that contain special characters like spaces.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Sources disagree (Low–High)AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Impact
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.
Workarounds
Install the application to a path without spaces, or to a location where all ancestor directories are protected against unauthorized writes.
Fixed Versions
41.0.0-beta.840.8.039.8.138.8.6
For more information
If there are any questions or comments about this advisory, send an email to [security@electronjs.org](mailto:security@electronjs.org)
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
GHSA-jfqx-fxh3-c62j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB