CVE-2026-34775
Electronjs Electron ≤ 38.8.6
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NSummary
CVE-2026-34775 is a medium-severity Improper Isolation or Compartmentalization (CWE-653) vulnerability in Electronjs Electron. Its CVSS base score is 6.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Escape to Host (T1611); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-2 (Separation of System and User Functionality) and SC-3 (Security Function Isolation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-34775 is a vulnerability in the Electron framework, used for developing cross-platform desktop applications with JavaScript, HTML, and CSS. Prior to versions 38.8.6, 39.8.4, 40.8.4, and 41.0.0, the nodeIntegrationInWorker webPreference is not correctly scoped in all configurations. In certain process-sharing scenarios, this allows workers spawned in frames configured with nodeIntegrationInWorker: false to still receive Node.js integration. Only Electron applications that enable nodeIntegrationInWorker are affected; those that do not use this option remain unaffected.
Remote attackers with no privileges can exploit this issue via network access, though it requires high attack complexity and user interaction, as indicated by its CVSS v3.1 score of 6.8 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N) and association with CWE-653. Exploitation involves scenarios where a user interacts with malicious content in an affected application, potentially enabling the attacker to inject or spawn workers that gain unauthorized Node.js integration despite frame-level restrictions. Successful exploitation leads to high confidentiality and integrity impacts, such as unauthorized access to Node.js APIs.
The Electron security advisory (GHSA-xwr5-m59h-vwqr) at https://github.com/electron/electron/security/advisories/GHSA-xwr5-m59h-vwqr confirms the patch in versions 38.8.6, 39.8.4, 40.8.4, and 41.0.0, resolving the scoping issue for nodeIntegrationInWorker. Mitigation involves updating to these patched versions and reviewing application configurations to ensure nodeIntegrationInWorker is enabled only where necessary.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-18949
Vulnerability Data
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.4, 40.8.4, and 41.0.0, the nodeIntegrationInWorker webPreference was not correctly scoped in all configurations. In certain process-sharing scenarios, workers spawned in frames…
more
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. This issue has been patched in versions 38.8.6, 39.8.4, 40.8.4, and 41.0.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 8 hardening rules · 7 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Security function isolation is the canonical mechanism for protecting higher-privilege compartments.
Process isolation maintains separate execution domains so one process cannot affect another’s privilege level.
Explicit separation of user and management functionality implements the required compartmentalization.
System partitioning creates distinct domains that enforce isolation between differently privileged components.
Access enforcement directly requires approved authorizations to be applied to compartmentalized resources.
Information flow enforcement structurally prevents unauthorized mixing of data or functions across privilege boundaries.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Segregation of duties directly enforces separation of privilege levels and functions.
Network segregation is a classic technical control for isolating different privilege domains.
Secure system architecture principles explicitly call for isolation and least-privilege boundaries.
Separation of development, test and production environments is a direct application of compartmentalization.
Access control policies establish the boundaries that isolation must enforce.
Managing access rights is the operational mechanism for compartmentalizing privileges.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 9 (1 rule)
- V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-653
RHEL 9 (2 rules)
- V-258078 RHEL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-653
- V-272496 RHEL 9 must elevate the SELinux context when an administrator calls the sudo command. prevents CWE-653
Windows 10 (1 rule)
- V-220712 Only accounts responsible for the administration of a system must have Administrator rights on the system. prevents CWE-653
Windows 11 (1 rule)
- V-253269 Only accounts responsible for the administration of a system must have Administrator rights on the system. prevents CWE-653
Windows Server 2016 (1 rule)
- V-225007 Only administrators responsible for the member server or standalone or nondomain-joined system must have Administrator rights on the system. prevents CWE-653