Electron: HTTP redirect followed into local file loader
Published 5 Aug 2026 · Updated 5 Aug 2026
Affected packages
- Affected
- <39.8.8
- Fixed in
- 39.8.8
npm install electron@39.8.8- Affected
- >=40.0.0-alpha.1 <40.9.1
- Fixed in
- 40.9.1
npm install electron@40.9.1- Affected
- >=41.0.0-alpha.1 <41.2.1
- Fixed in
- 41.2.1
npm install electron@41.2.1- Affected
- >=42.0.0-alpha.1 <42.0.0-beta.3
- Fixed in
- 42.0.0-beta.3
npm install electron@42.0.0-beta.3Details
Impact
When following HTTP redirects, net.fetch() and net.request() did not restrict which schemes a redirect could target. A remote server could redirect a request to a local resource, and if the app returns or forwards the response body, local file contents could be disclosed.
Apps are only affected if they make net requests to attacker-influenced URLs with redirects followed (the default) and expose the response body. Apps that only request fixed, trusted URLs are not affected.
Workarounds
Set redirect: 'error' or redirect: 'manual' on requests to untrusted URLs and validate any redirect target before following it.
Fixed Versions
42.0.0-beta.341.2.140.9.039.8.8
For more information
If you have any questions or comments about this advisory, email Electron at [security@electronjs.org](mailto:security@electronjs.org)
Is GHSA-v64r-4m7r-3mvq 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.