# CVE-2020-1059: Microsoft Edge Spoofing Vulnerability

> Attackers can trick users into visiting malicious sites via spoofed URLs, potentially enabling phishing or chained attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C`)
- **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:** No
- **Published:** 21 May 2020
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-mvgv-j2f5-78mw

## What is CVE-2020-1059?

CVE-2020-1059 is a medium-severity vulnerability in Microsoft Edge, published on 21 May 2020. 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

A spoofing vulnerability exists when Microsoft Edge does not properly parse HTTP content. An attacker who successfully exploited this vulnerability could trick a user by redirecting the user to a specially crafted website. The specially crafted website could either spoof content or serve as a pivot to chain an attack with other vulnerabilities in web services.
To exploit the vulnerability, the user must click a specially crafted URL. In an email attack scenario, an attacker could send an email message containing the specially crafted URL to the user in an attempt to convince the user to click it.
In a web-based attack scenario, an attacker could host a specially crafted website designed to appear as a legitimate website to the user. However, the attacker would have no way to force the user to visit the specially crafted website. The attacker would have to convince the user to visit the specially crafted website, typically by way of enticement in an email or instant message, and then convince the user to interact with content on the website.
The update addresses the vulnerability by correcting how Microsoft Edge parses HTTP responses.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Microsoft Edge.

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

No fix has been published for CVE-2020-1059 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-1059 being exploited?

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

## Other vulnerabilities in Microsoft Edge

- [CVE-2021-26411](https://insights.sbomify.com/CVE-2021-26411/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7200](https://insights.sbomify.com/CVE-2016-7200/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7201](https://insights.sbomify.com/CVE-2016-7201/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2017-0037](https://insights.sbomify.com/CVE-2017-0037/): Microsoft Edge and Internet Explorer Type Confusion (high 8.1, exploited in the wild)
- [CVE-2016-3351](https://insights.sbomify.com/CVE-2016-3351/): Microsoft Internet Explorer and Edge Information Disclosure (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1059 is a medium-severity vulnerability in Microsoft Edge, published on 21 May 2020. 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-2020-1059 in the wild and no public exploit code.

Affected product: Microsoft Edge. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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