ASAR Integrity bypass via filetype confusion in electron
Published 1 Dec 2023 · Updated 10 Sept 2026
Affected packages
- Affected
- <22.3.24
- Fixed in
- 22.3.24
npm install electron@22.3.24- Affected
- >=24.0.0-alpha.1 <24.8.3
- Fixed in
- 24.8.3
npm install electron@24.8.3- Affected
- >=25.0.0-alpha.1 <25.8.1
- Fixed in
- 25.8.1
npm install electron@25.8.1- Affected
- >=26.0.0-alpha.1 <26.2.1
- Fixed in
- 26.2.1
npm install electron@26.2.1- Affected
- >=27.0.0-alpha.1 <27.0.0-alpha.7
- Fixed in
- 27.0.0-alpha.7
npm install electron@27.0.0-alpha.7- Affected
- >=23.0.0-alpha.1 <=23.3.13
- Fixed in
- No fix released
Details
Impact
This only impacts apps that have the embeddedAsarIntegrityValidation and onlyLoadAppFromAsar fuses enabled. Apps without these fuses enabled are not impacted. This issue is specific to macOS as these fuses are only currently supported on macOS.
Specifically this issue can only be exploited if your app is launched from a filesystem the attacker has write access too. i.e. the ability to edit files inside the resources folder in your app installation on Windows which these fuses are supposed to protect against.
Workarounds
There are no app side workarounds, you must update to a patched version of Electron.
Fixed Versions
27.0.0-alpha.726.2.125.8.124.8.322.3.24
For more information
If you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org)
Is GHSA-7m48-wc93-9g85 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.