CVE-2026-102673: Electron drops inherited HTML sandbox restrictions for popups opened through OpenURLFromTab
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: electron (npm) 42.5.2, 43.0.0, 41.10.4.
- Severity is disputed: the assigning authority (CNA) scores it 8.2, NVD 6.1.
Low priority for now. Upgrade to electron (npm) 42.5.2, 43.0.0, 41.10.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 41.10.4, 42.5.2, and 43.0.0, popups opened from a sandboxed iframe through Electron's OpenURLFromTab navigation path, including links using target="_blank" or a middle-click, did not receive the inherited HTML sandbox restrictions. An untrusted iframe using the allow-scripts allow-popups configuration could therefore open a popup with the embedding application's full origin, exposing that origin's cookies, storage, and same-origin scripting capabilities. Applications that do not embed untrusted content in sandboxed iframes are not affected. This issue is fixed in versions 41.10.4, 42.5.2, and 43.0.0.
- Published
- Sep 29, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-346
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.1
- CNA · GitHub_M
- 8.2
- 2.1 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| electronjs | electron | cpe:2.3:a:electronjs:electron |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
electron electron
- < 41.10.4, >= 42.0.0-alpha.1, < 42.5.2, >= 43.0.0-alpha.1, < 43.0.0affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- electronjs electronbefore 39.8.8
- electronjs electron40.0.0 and later · before 40.9.0
- electronjs electron41.0.0 and later · up to 41.2.1 inclusive
- electronjs electron42.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | electron | from 42.0.0-alpha.1 · before 42.5.2 | 42.5.2 |
| npm | electron | from 43.0.0-alpha.1 · before 43.0.0 | 43.0.0 |
| npm | electron | before 41.10.4 | 41.10.4 |
Same product
electronjs: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-16151Based on details posted by the ElectronJS team; A remote code execution vulnerability has been discovered in Google Chromium that affects…40Plan
- CVE-2026-102676Electron: <webview> can enable Node.js integration in Web Workers despite embedder restrictions39Monitor
- CVE-2026-34775Electron: nodeIntegrationInWorker not correctly scoped in shared renderer processes39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-70611Aug 5, 2026 · Electron: DevTools embedder handler executes arbitrary files via shell open27Monitor
- ← EarlierCVE-2026-70612Aug 5, 2026 · Electron: Sandboxed iframes can launch external protocol handlers21Monitor
- Later →CVE-2026-102674Sep 29, 2026 · Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:electron | 41.10.4 | Package registry (OSV) |
| npm:electron | 42.5.2 | Package registry (OSV) |
| npm:electron | 43.0.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 16, 2026+48 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1026750 days apartElectron: File and HTTP protocol handlers allow cross-origin reads without corsEnabled29Monitor
- CVE-2026-7059955 days apartElectron: Permission Check Handler Receives Main Frame Origin Instead of Requesting Iframe Origin23Monitor
- CVE-2026-34777179 days apartElectron: Incorrect origin passed to permission request handler for iframe requests21Monitor
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-346 · Origin Validation ErrorCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Exploit Script-Based APIsCAPEC-160Medium
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
ATT&CK techniques
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Adversary-in-the-Middle: ARP Cache PoisoningT1557.002
- Compromise Infrastructure: DNS ServerT1584.002
Change log
- CVSS8.2 → 6.1
- Severityhigh → medium
- SSVC exploitation— → none
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- github.com/electron/electron/commit/e26b2640e7795c42bfb111b76009cbb4327c9a69
- github.com/electron/electron/commit/ebe1165ee2b05c203c26dd2244ef1c5b9b1c04da
- github.com/electron/electron/pull/52133
- github.com/electron/electron/releases/tag/v41.10.4
- github.com/electron/electron/releases/tag/v42.5.2
- github.com/electron/electron/releases/tag/v43.0.0
- github.com/electron/electron/security/advisories/GHSA-hq2x-r82h-9wj4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.