Electron: AppleScript injection in app.moveToApplicationsFolder on macOS
Published 3 Apr 2026 · Updated 6 Apr 2026
Affected packages
- Affected
- <38.8.6
- Fixed in
- 38.8.6
npm install electron@38.8.6- Affected
- >=39.0.0-alpha.1 <39.8.1
- Fixed in
- 39.8.1
npm install electron@39.8.1- Affected
- >=40.0.0-alpha.1 <40.8.0
- Fixed in
- 40.8.0
npm install electron@40.8.0- Affected
- >=41.0.0-alpha.1 <41.0.0-beta.8
- Fixed in
- 41.0.0-beta.8
npm install electron@41.0.0-beta.8Details
Impact
On macOS, app.moveToApplicationsFolder() used an AppleScript fallback path that did not properly handle certain characters in the application bundle path. Under specific conditions, a crafted launch path could lead to arbitrary AppleScript execution when the user accepted the move-to-Applications prompt.
Apps are only affected if they call app.moveToApplicationsFolder(). Apps that do not use this API are not affected.
Workarounds
There are no app side workarounds, developers must update to a patched version of Electron.
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, please email [security@electronjs.org](mailto:security@electronjs.org)
Is GHSA-5rqw-r77c-jp79 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected electron, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.