# CVE-2026-102673: Electron drops inherited HTML sandbox restrictions for popups opened through OpenURLFromTab

> Attackers can bypass sandbox restrictions in Electron popups to access sensitive origin data and execute scripts if untrusted content is embedded.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-hq2x-r82h-9wj4

## What is CVE-2026-102673?

CVE-2026-102673 is a high-severity vulnerability in Electronjs Electron, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-102673?

6 open source packages ship an affected version, including electron. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `electron` | npm | All versions | 41.10.4 |
| `electron` | npm | All versions | 41.10.4 |
| `electron` | npm | From 42.0.0-alpha.1 | 42.5.2 |
| `electron` | npm | From 42.0.0-alpha.1 | 42.5.2 |
| `electron` | npm | From 43.0.0-alpha.1 | 43.0.0 |
| `electron` | npm | From 43.0.0-alpha.1 | 43.0.0 |

Products: Electronjs Electron.

## How do I fix CVE-2026-102673?

Upgrade electron to a fixed version for your release line: 41.10.4, 42.5.2 or 43.0.0.

## Is CVE-2026-102673 being exploited?

There is no known exploitation of CVE-2026-102673 in the wild and no public exploit code.

## Other vulnerabilities in Electronjs Electron

- [CVE-2017-16151](https://insights.sbomify.com/CVE-2017-16151/): Chromium Remote Code Execution in electron (critical 9.8)
- [CVE-2018-1000118](https://insights.sbomify.com/CVE-2018-1000118/): Electron protocol handler browser vulnerable to Command Injection (high 8.8)
- [CVE-2026-34780](https://insights.sbomify.com/CVE-2026-34780/): Electron: Context Isolation bypass via contextBridge VideoFrame transfer (high 8.4)
- [CVE-2026-102676](https://insights.sbomify.com/CVE-2026-102676/): Electron: <webview> can enable Node.js integration in Web Workers despite embedder restrictions (high 8.3)
- [CVE-2026-102674](https://insights.sbomify.com/CVE-2026-102674/): Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102673 and fix it if it is affected.

What it is: CVE-2026-102673 is a high-severity vulnerability in Electronjs Electron, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-102673 in the wild and no public exploit code.

Affected packages and fixed versions:
- electron (npm): affected all versions; fixed in 41.10.4
- electron (npm): affected all versions; fixed in 41.10.4
- electron (npm): affected from 42.0.0-alpha.1; fixed in 42.5.2
- electron (npm): affected from 42.0.0-alpha.1; fixed in 42.5.2
- electron (npm): affected from 43.0.0-alpha.1; fixed in 43.0.0
- electron (npm): affected from 43.0.0-alpha.1; fixed in 43.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102673/ (Markdown: https://insights.sbomify.com/CVE-2026-102673/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102673
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102673
- OSV: https://osv.dev/vulnerability/CVE-2026-102673

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102673/
Summaries are generated and may contain mistakes; the official description above is the record.