CVE-2026-34780
Electronjs Electron 39.0.0 – 39.8.0
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2026-34780 is a high-severity Exposure of Resource to Wrong Sphere (CWE-668) vulnerability in Electronjs Electron. Its CVSS base score is 8.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Default Accounts (T1078.001); ranked at the 25th 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 AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — 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.
Electron, a framework for developing cross-platform desktop applications using JavaScript, HTML, and CSS, is affected by CVE-2026-34780, a context isolation bypass vulnerability. This flaw impacts versions 39.0.0-alpha.1 through 39.7.999 (before 39.8.0), 40.0.0-alpha.1 through 40.6.999 (before 40.7.0), and 41.0.0-alpha.1 through 41.0.0-beta.7 (before 41.0.0-beta.8). It arises when applications pass VideoFrame objects from the WebCodecs API across the contextBridge, enabling unauthorized access between isolated renderer contexts and the main process.
An attacker who can execute arbitrary JavaScript in the main world—for instance, via cross-site scripting (XSS)—can leverage a bridged VideoFrame object to breach context isolation and access the isolated world. This grants privileges to any Node.js APIs exposed by the preload script. Exploitation requires the target application to explicitly return, resolve, or pass VideoFrame objects to the main world via contextBridge.exposeInMainWorld(); applications that do not bridge these objects are unaffected. The vulnerability carries a CVSS v3.1 base score of 8.3 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) and is associated with CWEs 668 (Exposure of Resource to Wrong Sphere) and 1188 (Insecure Default Initialization of Resource).
The official Electron security advisory (GHSA-jfqg-hf23-qpw2) at https://github.com/electron/electron/security/advisories/GHSA-jfqg-hf23-qpw2 confirms the issue and states that it has been addressed in Electron versions 39.8.0, 40.7.0, and 41.0.0-beta.8. Practitioners should verify and upgrade affected Electron-based applications to these patched releases or later to eliminate the bypass risk.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-18961
Vulnerability Data
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From versions 39.0.0-alpha.1 to before 39.8.0, 40.0.0-alpha.1 to before 40.7.0, and 41.0.0-alpha.1 to before 41.0.0-beta.8, apps that pass VideoFrame objects (from the WebCodecs API) across the…
more
contextBridge are vulnerable to a context isolation bypass. An attacker who can execute JavaScript in the main world (for example, via XSS) can use a bridged VideoFrame to gain access to the isolated world, including any Node.js APIs exposed to the preload script. Apps are only affected if a preload script returns, resolves, or passes a VideoFrame object to the main world via contextBridge.exposeInMainWorld(). Apps that do not bridge VideoFrame objects are not affected. This issue has been patched in versions 39.8.0, 40.7.0, and 41.0.0-beta.8.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 21 hardening rules · 9 OS baselines
V14.3.2V6.3.2V11.3.1V13.2.3
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops resources from being reachable by actors outside the intended control sphere.
Information flow enforcement structurally prevents unintended cross-sphere data or resource exposure.
Least privilege reduces the set of actors that can reach a resource, limiting wrong-sphere exposure.
Baseline configuration directly requires documenting and maintaining secure initial settings instead of insecure defaults.
Configuration settings mandate the most restrictive values be applied at initialization, eliminating reliance on insecure factory defaults.
Security attributes enable correct sphere assignment and subsequent enforcement decisions.
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.
Hardened baselines and configuration management directly replace insecure defaults with secure settings.
Enforcing least-privilege authorizations directly prevents resources from being exposed outside their intended control sphere.
Secure development practices include designing products with secure defaults rather than insecure ones.
Documented data-flow representations make trust boundaries explicit and help surface mixing of trusted/untrusted data.
Pre-acquisition integrity checks can reject products known to ship with insecure defaults.
Network segmentation and unauthorized-access protections reduce the chance of resources being reachable by the wrong sphere.
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.
Secure architecture principles require explicit trust zones and data segregation, mitigating mixing of trusted/untrusted data.
Secure coding standards can enforce input validation and data tagging, but do not guarantee architectural separation.
Mandating secure baseline templates and immediate replacement of vendor defaults directly stops systems from being deployed with insecure factory settings that attackers can exploit.
Placing systems of differing trust levels into separate domains prevents resources from being placed in a sphere where they are reachable by unintended actors.
Secure development lifecycle mandates separation of trusted and untrusted data flows, directly preventing mixing in the same structure.
Application security requirements include explicit trust-boundary definitions and data classification at interfaces.
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 8 (2 rules)
- V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-668
- V-248823 OL 8 must not have the telnet-server package installed. prevents CWE-1188, CWE-668
RHEL 7 (2 rules)
- V-204627 SNMP community strings on the Red Hat Enterprise Linux operating system must be changed from the default. prevents CWE-1188
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-668
Ubuntu 22.04 (1 rule)
- V-260529 Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-1188
Ubuntu 24.04 (1 rule)
- V-270708 Ubuntu 24.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-1188
Windows 10 (1 rule)
- V-220967 The Debug programs user right must only be assigned to the Administrators group. prevents CWE-668
Windows 11 (1 rule)
- V-253490 The "Debug programs" user right must only be assigned to the Administrators group. prevents CWE-668
Windows Server 2016 (2 rules)
- V-224972 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-1188
- V-225079 The Debug programs user right must only be assigned to the Administrators group. prevents CWE-668
Windows Server 2019 (2 rules)
- V-205741 Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-1188
- V-205757 Windows Server 2019 Debug programs: user right must only be assigned to the Administrators group. prevents CWE-668
Windows Server 2022 (1 rule)
- V-254500 Windows Server 2022 debug programs user right must only be assigned to the Administrators group. prevents CWE-668