GHSA-xwr5-m59h-vwqr
MEDIUMGHSA-xwr5-m59h-vwqr is a medium-severity (CVSS 6.8) CWE-653 vulnerability in electron. O3 Security confirms whether GHSA-xwr5-m59h-vwqr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Electron: nodeIntegrationInWorker not correctly scoped in shared renderer processes
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
electronnpmDescription
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.040.8.439.8.438.8.6
For more information
If there are any questions or comments about this advisory, please email [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | electron | all versions | 38.8.6 |
| 📦npm | electron | ≥ 39.0.0-alpha.1&&< 39.8.4 | 39.8.4 |
| 📦npm | electron | ≥ 40.0.0-alpha.1&&< 40.8.4 | 40.8.4 |
| 📦npm | electron | ≥ 41.0.0-alpha.1&&< 41.0.0 | 41.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update electron to 38.8.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwr5-m59h-vwqr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xwr5-m59h-vwqr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-xwr5-m59h-vwqr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xwr5-m59h-vwqr in your dependencies?
O3 detects GHSA-xwr5-m59h-vwqr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.