Skip to content
Fencer Vulns
low 3.9

CVE-2026-34768 json

Electron: Unquoted executable path in app.setLoginItemSettings on Windows

published 2026-04-03 7 mo ago modified 2026-07-24 3 mo ago also EUVD-2026-18935 , GHSA-jfqx-fxh3-c62j

cvss
3.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm electron 38.8.6, 39.8.1, 40.8.0, 41.0.0-beta.8
  • atom electron 38.8.6, 39.8.1, 40.8.0, 41.0.0-beta.8
  • electronjs electron 38.8.6, 39.8.1, 40.8.0, 41.0.0-beta.8

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-34768 updated cvss 3.9

electron: Electron: Arbitrary code execution via unquoted path in Run registry key

  • Red Hat Build of Podman Desktop podman-desktop-macos-1-0, podman-desktop-windows-1-0 Red Hat Build of Podman Desktop - Tech Preview rhdesktop/rh-podman-desktop-ext-openshift-local-rhel10
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7 mo ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.9 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
GitHub 3.1 3.9 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm electron
<38.8.6
>=39.0.0-alpha.1, <39.8.1
>=40.0.0-alpha.1, <40.8.0
>=41.0.0-alpha.1, <41.0.0-beta.8
38.8.6
39.8.1
40.8.0
41.0.0-beta.8

Affected products

  • electron electron

Classification

Weakness
  • CWE-428 Unquoted Search Path or Element

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.