MediumGHSA-vmqv-hx8q-j7mgCVE-2025-55305

Electron has ASAR Integrity Bypass via resource modification

Published 3 Sept 2025 · Updated 5 Sept 2025

Affected packages

electronnpm

Affected: <35.7.5
Fixed in: 35.7.5

Update to the fixed version for your release line, for example:npm install electron@35.7.5

electronnpm

Affected: >=36.0.0-alpha.1 <36.8.1
Fixed in: 36.8.1

Update to the fixed version for your release line, for example:npm install electron@36.8.1

electronnpm

Affected: >=37.0.0-alpha.1 <37.3.1
Fixed in: 37.3.1

Update to the fixed version for your release line, for example:npm install electron@37.3.1

electronnpm

Affected: >=38.0.0-alpha.1 <38.0.0-beta.6
Fixed in: 38.0.0-beta.6

Update to the fixed version for your release line, for example:npm install electron@38.0.0-beta.6

Details

Impact

This only impacts apps that have the embeddedAsarIntegrityValidation and onlyLoadAppFromAsar fuses enabled. Apps without these fuses enabled are not impacted.

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

38.0.0-beta.6
37.3.1
36.8.1
35.7.5

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-vmqv-hx8q-j7mg 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.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.