MediumGHSA-xwr5-m59h-vwqrCVE-2026-34775

Electron: nodeIntegrationInWorker not correctly scoped in shared renderer processes

Published 3 Apr 2026 · Updated 6 Apr 2026

Affected packages

Affected
<38.8.6
Fixed in
38.8.6
Update to the fixed version for your release line, for example:npm install electron@38.8.6
Affected
>=39.0.0-alpha.1 <39.8.4
Fixed in
39.8.4
Update to the fixed version for your release line, for example:npm install electron@39.8.4
Affected
>=40.0.0-alpha.1 <40.8.4
Fixed in
40.8.4
Update to the fixed version for your release line, for example:npm install electron@40.8.4
Affected
>=41.0.0-alpha.1 <41.0.0
Fixed in
41.0.0
Update to the fixed version for your release line, for example:npm install electron@41.0.0

Details

Impact

The nodeIntegrationInWorker webPreference was not correctly scoped in all configurations. In certain process-sharing scenarios, workers spawned in frames configured with nodeIntegrationInWorker: false could still receive Node.js integration.

Apps are only affected if they enable nodeIntegrationInWorker. Apps that do not use nodeIntegrationInWorker are not affected.

Workarounds

Avoid enabling nodeIntegrationInWorker in apps that also open child windows or embed content with differing webPreferences.

Fixed Versions

  • 41.0.0
  • 40.8.4
  • 39.8.4
  • 38.8.6

For more information

If there are any questions or comments about this advisory, please email [security@electronjs.org](mailto:security@electronjs.org)

Is GHSA-xwr5-m59h-vwqr 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.