Electron: Off-screen rendering trusts GPU-supplied geometry over shared-memory size
Published 5 Aug 2026 · Updated 5 Aug 2026
Affected packages
- Affected
- <39.8.10
- Fixed in
- 39.8.10
npm install electron@39.8.10- Affected
- >=40.0.0-alpha.1 <40.9.0
- Fixed in
- 40.9.0
npm install electron@40.9.0- 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
In offscreen rendering mode, frame data received from the GPU process was not fully validated by the main process. A compromised GPU process could cause the main process to read out-of-bounds memory while producing paint event images, disclosing memory or crashing the app.
Apps are only affected if they use offscreen rendering (webPreferences.offscreen) and an attacker has separately gained code execution in the GPU process. Apps that do not use offscreen rendering are not affected.
Workarounds
There are no app side workarounds, you must update to a patched version of Electron.
Fixed Versions
42.0.0-beta.341.2.140.9.039.8.10
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-pfmc-3mgc-p6fp 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.