HighGHSA-j84w-jfhq-vhvjCVE-2026-102675

Electron: File and HTTP protocol handlers allow cross-origin reads without corsEnabled

Published 29 Sept 2026 · Updated 29 Sept 2026

Affected packages

Affected
<41.10.6
Fixed in
41.10.6
Update to the fixed version for your release line, for example:npm install electron@41.10.6
Affected
>=42.0.0-alpha.1 <42.9.2
Fixed in
42.9.2
Update to the fixed version for your release line, for example:npm install electron@42.9.2
Affected
>=43.0.0-alpha.1 <43.4.1
Fixed in
43.4.1
Update to the fixed version for your release line, for example:npm install electron@43.4.1
Affected
>=44.0.0-alpha.1 <44.0.0-beta.5
Fixed in
44.0.0-beta.5
Update to the fixed version for your release line, for example:npm install electron@44.0.0-beta.5

Details

Impact

Responses served through protocol.registerFileProtocol or protocol.registerHttpProtocol for a custom scheme registered with supportFetchAPI: true but without corsEnabled: true could be read cross-origin by web content. This completes the fix for CVE-2026-70604.

Apps are only affected if they register such a scheme, serve it through one of those handlers, and load untrusted content. Apps that set corsEnabled: true, or that do not load untrusted content, are not affected.

Workarounds

Set corsEnabled: true on the scheme, or do not load untrusted content in windows that can reach it.

Fixed Versions

  • 44.0.0-beta.5
  • 43.4.1
  • 42.9.2
  • 41.10.6

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-j84w-jfhq-vhvj 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.