HighGHSA-qmv3-fv6v-rmhqCVE-2026-102677

Electron: Sandboxed preload code cache can be poisoned by a compromised renderer

Published 29 Sept 2026 · Updated 29 Sept 2026

Affected packages

electronnpm
Affected
>=42.3.3 <42.10.0
Fixed in
42.10.0
Update to the fixed version for your release line, for example:npm install electron@42.10.0
electronnpm
Affected
>=43.0.0-beta.1 <43.5.0
Fixed in
43.5.0
Update to the fixed version for your release line, for example:npm install electron@43.5.0
electronnpm
Affected
>=44.0.0-alpha.1 <44.0.0-beta.6
Fixed in
44.0.0-beta.6
Update to the fixed version for your release line, for example:npm install electron@44.0.0-beta.6

Details

Impact

The cache Electron keeps for sandboxed preload scripts did not verify that a cached entry matched the preload it was served for. A compromised renderer could use this to run its own code in the preload context on a later load.

Apps are only affected if they load untrusted content. Apps that do not load untrusted content are not affected.

Workarounds

There are no app side workarounds, you must update to a patched version of Electron.

Fixed Versions

  • 44.0.0-beta.6
  • 43.5.0
  • 42.10.0

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-qmv3-fv6v-rmhq 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 signupOr connect GitHub to scan every repo

References

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