CVE-2026-34768 | Electron: Unquoted executable path in app.setLoginItemSettings on Windows

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.

Published: 2026-04-04 Last update: 2026-04-09 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-34768 is rated Low Risk (16.7/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.13%). Mandatory action: Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-34768

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.13% +0.12%
2 2026-04-04 0.01%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-34768

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.9 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
0.5 3.4 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 5.9 [email protected]

Weakness enumeration for CVE-2026-34768

GitHub Security Advisory for CVE-2026-34768

GHSA-jfqx-fxh3-c62j · Severity: low · Ecosystem: npm — Electron: Unquoted executable path in app.setLoginItemSettings on Windows

OS Trackers for CVE-2026-34768

vendor priority summary link
redhat low https://access.redhat.com/security/cve/CVE-2026-34768

Affected software / configurations for CVE-2026-34768

Vendor Product Version Raw CPE
electronjs electron < 38.8.6 cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:*
electronjs electron >= 39.0.0, < 39.8.1 cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:*
electronjs electron >= 40.0.0, < 40.8.0 cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:alpha1:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:alpha2:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:alpha3:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:alpha4:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:alpha5:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:alpha6:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:beta1:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:beta2:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:beta3:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:beta4:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:beta5:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:beta6:*:*:*:node.js:*:*
electronjs electron 41.0.0 cpe:2.3:a:electronjs:electron:41.0.0:beta7:*:*:*:node.js:*:*

References for CVE-2026-34768

cvelogic Threat Intelligence