# CVE-2020-4075: Arbitrary file read via window-open IPC in Electron

> Attackers can read arbitrary local files by exploiting unsafe window options in child windows opened via window.open in Electron applications.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f9mq-jph6-9mhm

## What is CVE-2020-4075?

CVE-2020-4075 is a medium-severity path traversal vulnerability in Electronjs Electron, published on 7 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened via window.open. As a workaround, ensure you are calling `event.preventDefault()` on all new-window events where the `url` or `options` is not something you expect. This is fixed in versions 9.0.0-beta.21, 8.2.4 and 7.2.4.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2020-4075?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `electron` | npm | All versions | 7.2.4 |
| `electron` | npm | All versions | 7.2.4 |
| `electron` | npm | From 8.0.0 | 8.2.4 |
| `electron` | npm | From 8.0.0 | 8.2.4 |

Products: Electronjs Electron.

## How do I fix CVE-2020-4075?

Upgrade electron to a fixed version for your release line: 7.2.4 or 8.2.4.

## Is CVE-2020-4075 being exploited?

There is no known exploitation of CVE-2020-4075 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-102673](https://insights.sbomify.com/CVE-2026-102673/): Electron drops inherited HTML sandbox restrictions for popups opened through OpenURLFromTab (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-4075 and fix it if it is affected.

What it is: CVE-2020-4075 is a medium-severity path traversal vulnerability in Electronjs Electron, published on 7 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-4075 in the wild and no public exploit code.

Affected packages and fixed versions:
- electron (npm): affected all versions; fixed in 7.2.4
- electron (npm): affected all versions; fixed in 7.2.4
- electron (npm): affected from 8.0.0; fixed in 8.2.4
- electron (npm): affected from 8.0.0; fixed in 8.2.4

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-2020-4075/ (Markdown: https://insights.sbomify.com/CVE-2020-4075/index.md)
```

## Sources

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

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