Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker serves malicious page at iframe-loaded origin
-
DeliveryTarget Electron app loads content in sandboxed iframe (allow-scripts, no allow-popups)
-
ExploitIframe JS dispatches synthetic Ctrl+click on DOMContentLoaded
-
ExecutionOpenURL navigation path invoked without sandbox popup flag check
-
PersistNew BrowserWindow spawned outside iframe sandbox boundary
-
ImpactAttacker-controlled window displayed in trusted app context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
|
| Exploitation Conditions | Exploitation requires the Electron application to actively embed untrusted or third-party HTML content inside a sandboxed iframe where the |
| Impact | The CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) reflects network-reachable, unauthenticated exploitation with a scope change - the iframe sandbox boundary is escaped. In practice, real-world risk is conditional: only Electron applications that (1) embed untrusted or third-party content in sandboxed iframes and (2) rely solely on the iframe sandbox for popup prevention are affected. Applications using |
| Exploit ScenarioDerived | A threat actor serves a malicious webpage from an attacker-controlled origin that is embedded as a sandboxed iframe (with |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 05, 2026
Sandboxed iframe popup restriction bypass in Electron allows untrusted iframe content to open new windows or trigger setWindowOpenHandler without user interaction, despite the allow-popups keyword being absent from the sandbox attribute. Electron versions prior to 42.0.1, 41.10.3, and 39.8.10 are affected. The bypass occurs because FrameLoader::StartNavigation and WebContents::OpenURLFromTab in the OpenURL code path did not check the iframe's sandbox popup flags, permitting emulated Ctrl+click events from untrusted JavaScript to create new browsing contexts. No public exploit or CISA KEV listing is confirmed at time of analysis, but the patch diff includes a working proof-of-concept test.
RemediationAI
Upgrade Electron to the appropriate patched release: 42.0.1, 41.10.3, or 39.8.10 depending on your current release line. Patches are merged via pull requests #51437, #51438, and #51439 against the corresponding branches. Where immediate upgrade is not feasible, the vendor-recommended workaround is to return { action: 'deny' } from setWindowOpenHandler for any content that is not fully trusted - this ensures even if the sandbox bypass fires, the resulting window creation is blocked at the Electron API layer. This workaround has no functional side effects for applications that already intend to deny external window creation, but may suppress legitimately expected popups in applications that selectively allow them; review your setWindowOpenHandler logic carefully before applying it broadly. Relying solely on the iframe sandbox attribute without allow-popups as a popup prevention mechanism should be treated as insufficient on unpatched versions.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in npm, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Electron wraps Chromium's Blink rendering engine and exposes it through a Node.js-based desktop application framework (pkg:npm/electron). The HTML sandbox attribute restricts iframe capabilities; omitting allow-popups is supposed to prevent the iframe from opening new windows. The root cause (CWE-693, Protection Mechanism Failure) is a missing sandbox flag check in two Chromium/Electron code paths: FrameLoader::StartNavigation (Blink-level) and WebContents::OpenURLFromTab (Electron-level). When an untrusted event such as a programmatically dispatched Ctrl+click MouseEvent triggers a new-tab navigation (kNavigationPolicyNewForegroundTab), the code routed through OpenURL skipped the WebSandboxFlags::kPopups check entirely. The fix adds an explicit check in both frame_loader.cc (for kFromUntrustedEvent navigation policy) and electron_api_web_contents.cc (checking SandboxFlags::kPopups on the initiating frame tree node before allowing OpenURLFromTab to proceed). The affected npm package ranges are: >= 42.0.0-alpha.1, < 42.0.1; >= 40.0.0-alpha.1, < 41.10.3; and < 39.8.10.
Know when the next one hits your stack
- 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
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Network-delivered iframe content requires no app privileges; untrusted event auto-fires with no user gesture; scope changes as sandbox boundary is crossed; no availability impact.
Primary rating from Vendor (https://github.com/electron/electron).
CVSS VectorVendor: https://github.com/electron/electron
DescriptionCVE.org
Impact
A sandboxed iframe without the allow-popups keyword could still open a new window (or trigger setWindowOpenHandler) with no user interaction, because new-window navigations taking the OpenURL path did not apply the iframe sandbox popup restriction.
Apps that embed untrusted content in sandboxed iframes and rely on the absence of allow-popups to prevent window creation are affected. Apps that deny window creation in setWindowOpenHandler, or that do not embed untrusted content in sandboxed iframes, are not affected.
Workarounds
Return { action: 'deny' } from setWindowOpenHandler for any content you do not trust, rather than relying on the iframe sandbox alone.
Fixed Versions
42.0.141.10.339.8.10
For more information
If you have any questions or comments about this advisory, email Electron at [security@electronjs.org](mailto:security@electronjs.org)
Executive ViewAI
Electron versions prior to 42.0.1, 41.10.3, and 39.8.10 contain a sandbox bypass vulnerability that allows untrusted iframe content to open new windows and trigger handlers without user interaction. This affects any organization using Electron-based applications (including developer tools, communication platforms, and enterprise software) that load third-party or untrusted web content. The vulnerability could enable phishing attacks, malware delivery, or unauthorized system access through compromised desktop applications deployed across your workforce.
Apply vendor patch.
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.
EUVD-2026-53564
GHSA-9f4c-93c8-jc8g
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB