Low

Electron: Unquoted executable path in app.setLoginItemSettings on Windows

  • Disclosed: 03.04.2026
  • Updated: 11.10.2026 10:22

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.8
  • 40.8.0
  • 39.8.1
  • 38.8.6

For more information

If there are any questions or comments about this advisory, send an email to security@electronjs.org

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package 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

References

CVSS score 3.9/10
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
Weakness (CWE)
CWE-428
Platform
npm
Package
electron
Disclosed
03.04.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-jfqx-fxh3-c62j - CC BY 4.0

Vulnerability history: electron

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (71) in the archive
Total entries
71
First → latest
10.2017 09.2026
Without a fix
0
Exploited in attacks
3

Severity breakdown

  • Critical 3
  • High 26
  • Medium 32
  • Low 10

Disclosures per year

  1. 2017: 1
  2. 2018: 5
  3. 2019: 0
  4. 2020: 6
  5. 2021: 2
  6. 2022: 7
  7. 2023: 6
  8. 2024: 0
  9. 2025: 3
  10. 2026: 41
Severity:
  1. High · 8.2 CVE-2026-102673 < 41.10.4, >= 42.0.0-alpha.1, < 42.5.2, >= 43.0.0-alpha.1, < 43.0.0 41.10.4, 42.5.2, 43.0.0
  2. High · 8.2 CVE-2026-102674 < 41.10.6, >= 42.0.0-alpha.1, < 42.9.2, >= 43.0.0-alpha.1, < 43.4.1, >= 44.0.0-alpha.1, < 44.0.0-beta.5 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  3. High · 7.4 CVE-2026-102675 < 41.10.6, >= 42.0.0-alpha.1, < 42.9.2, >= 43.0.0-alpha.1, < 43.4.1, >= 44.0.0-alpha.1, < 44.0.0-beta.5 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  4. High · 8.3 CVE-2026-102676 < 41.10.6, >= 42.0.0-alpha.1, < 42.9.2, >= 43.0.0-alpha.1, < 43.4.1, >= 44.0.0-alpha.1, < 44.0.0-beta.5 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  5. High · 7.8 CVE-2026-102677 >= 42.3.3, < 42.10.0, >= 43.0.0-beta.1, < 43.5.0, >= 44.0.0-alpha.1, < 44.0.0-beta.6 42.10.0, 43.5.0, 44.0.0-beta.6
  6. High · 7.2 CVE-2026-70608 >= 42.0.0-alpha.1, < 42.0.1, >= 40.0.0-alpha.1, < 41.10.3, < 39.8.10 42.0.1, 41.10.3, 39.8.10
  7. High · 7.4 CVE-2026-70604 >= 42.0.0-alpha.1, < 42.0.0, >= 41.0.0-alpha.1, < 41.4.0, >= 40.0.0-alpha.1, < 40.9.3, < 39.8.10 42.0.0, 41.4.0, 40.9.3, 39.8.10
  8. High · 7.5 CVE-2026-70601 < 39.8.9, >= 40.0.0-alpha.1, < 40.9.2, >= 41.0.0-alpha.1, < 41.2.2, >= 42.0.0-alpha.1, < 42.0.0-beta.5 39.8.9, 40.9.2, 41.2.2, 42.0.0-beta.5
  9. High · 8.3 CVE-2026-34780 >= 39.0.0-alpha.1, < 39.8.0, >= 40.0.0-alpha.1, < 40.7.0, >= 41.0.0-alpha.1, < 41.0.0-beta.8 39.8.0, 40.7.0, 41.0.0-beta.8
  10. High · 8.1 CVE-2026-34774 < 39.8.1, >= 40.0.0-alpha.1, < 40.7.0, >= 41.0.0-alpha.1, < 41.0.0 39.8.1, 40.7.0, 41.0.0
  11. High · 7.5 CVE-2026-34771 < 38.8.6, >= 39.0.0-alpha.1, < 39.8.0, >= 40.0.0-alpha.1, < 40.7.0, >= 41.0.0-alpha.1, < 41.0.0-beta.8 38.8.6, 39.8.0, 40.7.0, 41.0.0-beta.8
  12. High · 7.0 CVE-2026-34770 < 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
  13. High · 7.7 CVE-2026-34769 < 38.8.6, >= 39.0.0-alpha.1, < 39.8.0, >= 40.0.0-alpha.1, < 40.7.0, >= 41.0.0-alpha.1, < 41.0.0-beta.8 38.8.6, 39.8.0, 40.7.0, 41.0.0-beta.8
  14. Electron: Unquoted executable path in app.setLoginItemSettings on Windows this entry
    Low · 3.9 CVE-2026-34768 < 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
  15. High · 7.8 CVE-2024-46992 >= 30.0.0-alpha.1, < 30.0.5, >= 31.0.0-alpha.1, < 31.0.0-beta.1 30.0.5, 31.0.0-beta.1
  16. High · 8.8 Exploited in attacks CVE-2023-5217 < 22.3.25, >= 24.0.0, < 24.8.5, >= 25.0.0, < 25.8.4, >= 26.0.0, < 26.2.4, >= 27.0.0-alpha.1, < 27.0.0-beta.8 22.3.25, 24.8.5, 25.8.4, 26.2.4, 27.0.0-beta.8
  17. High · 8.8 Exploited in attacks CVE-2023-4863 >= 22.0.0, < 22.3.24, >= 24.0.0, < 24.8.3, >= 25.0.0, < 25.8.1, >= 26.0.0, < 26.2.1, >= 27.0.0-beta.1, < 27.0.0-beta.2 22.3.24, 24.8.3, 25.8.1, 26.2.1, 27.0.0-beta.2
  18. High · 7.5 CVE-2023-23623 >= 22.0.0-beta.1, < 22.0.1, >= 23.0.0-alpha.1, < 23.0.0-alpha.2 22.0.1, 23.0.0-alpha.2
  19. Critical · 9.6 Exploited in attacks CVE-2022-4135 >= 19.0.0, < 19.1.8 19.1.8
Show more (10) Showing 20 of 30

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.