CVE-2026-34768: low-severity vulnerability in electron
Electron: Unquoted executable path in app.setLoginItemSettings on Windows
Published · Updated
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 3.9epss 0.1%
exploitation probability
0.1%top 97% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
Affected products
electron · electronRelated CVEs — electron
In the same product, most dangerous first.
CVE-2020-26272MEDIUMElectron vulnerable to ID collision when routing IPC messages to renderers containing OOPIFsEPSS 1.7%CVE-2020-15174HIGHUnpreventable top-level navigation in ElectronEPSS 1.3%CVE-2020-4075MEDIUMArbitrary file read via window-open IPC in ElectronEPSS 1.2%CVE-2021-39184MEDIUMSandboxed renderers can obtain thumbnails of arbitrary files through the nativeImage APIEPSS 1.1%CVE-2022-29247LOWExposure of Resource to Wrong Sphere in ElectronEPSS 1.0%CVE-2020-4077HIGHContext isolation bypass via contextBridge in ElectronEPSS 1.0%