Node.js CVE-2026-34775
CRITICALVulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Component isolation
|
| Impact | The CVSS 6.8 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N) indicates network-accessible vulnerability requiring high attack complexity, user interaction, and no privileges-typical of browser-based attacks requiring social engineering or user click-through. Confidentiality and integrity are high-impact (information disclosure and code execution possible), but availability is not affected. The attack complexity is elevated, partially mitigating the risk; an attacker must craft a specific multi-frame configuration and trigger worker creation in a precisely scoped context. Critically, this vulnerability is opt-in-only applications that explicitly enable nodeIntegrationInWorker are vulnerable, significantly reducing real-world surface area. The requirement for user interaction (UI:R) further constrains practical exploitability. No public exploit code or active exploitation (KEV status) has been identified, and the complexity of the attack scenario suggests this is a lower-priority issue compared to simpler remote code execution vectors, despite the elevated CVSS score. |
| Exploit ScenarioDerived | An attacker could craft a malicious website that, when loaded by an Electron application with nodeIntegrationInWorker enabled, creates a child frame with nodeIntegrationInWorker: false and then spawns a Web Worker from that frame. Due to the scoping flaw, the worker would unexpectedly receive Node.js integration, allowing the attacker to execute arbitrary Node.js code and access the local filesystem, system processes, or other privileged operations. This requires the user to navigate to or be socially engineered into visiting the malicious site within a vulnerable Electron application. No public exploit code has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 03, 2026
Electron's nodeIntegrationInWorker webPreference fails to properly isolate Node.js integration in worker contexts across certain process-sharing configurations, allowing workers in frames explicitly configured with nodeIntegrationInWorker: false to unexpectedly gain Node.js capabilities. Only applications that explicitly enable nodeIntegrationInWorker are affected. The vulnerability carries a CVSS score of 6.8 and permits information disclosure and code execution in affected contexts, with no public exploit identified at time of analysis.
RemediationAI
Vendor-released patch: Electron 41.0.0, 40.8.4, 39.8.4, or 38.8.6 depending on the currently deployed major version. Application maintainers should upgrade to the corresponding patched version immediately. For applications unable to upgrade immediately, the primary workaround is to avoid enabling nodeIntegrationInWorker in applications that also open child windows or embed external content with differing webPreferences; alternatively, ensure all frames within a shared process have identical webPreferences configurations. Consult the GitHub security advisory at https://github.com/electron/electron/security/advisories/GHSA-xwr5-m59h-vwqr for detailed remediation guidance and version-specific upgrade paths.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Electron is a framework for building cross-platform desktop applications using web technologies (Chromium and Node.js). The nodeIntegrationInWorker webPreference controls whether Web Workers spawned within a renderer process have access to Node.js APIs. The vulnerability exists in the scoping mechanism that enforces this security boundary; when multiple frames with differing webPreferences are managed in a shared process context, the isolation logic fails to correctly propagate the nodeIntegrationInWorker: false setting to worker threads. This is fundamentally a CWE-653 (Insufficient Compartmentalization) issue-the security boundary between sandboxed and non-sandboxed execution contexts is not adequately enforced. The affected npm package is electron across versions prior to 41.0.0, 40.8.4, 39.8.4, and 38.8.6.
Know when Node.js gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
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 [security@electronjs.org](mailto:security@electronjs.org)
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)NVD
Related Vulnerabilities in Electron Security Vulnerabilities
View all 11Remote code execution in n8n's workflow expression evaluation system allows an authenticated user with workflow creation
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
GHSA-xwr5-m59h-vwqr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB