# CVE-2020-1040: Microsoft Hyper-V RemoteFX vGPU Remote Code Execution

> An authenticated guest user can trigger remote code execution on the Hyper-V host via improper input validation in RemoteFX vGPU.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-98qh-xxww-5r96

## What is CVE-2020-1040?

CVE-2020-1040 is a critical memory corruption vulnerability in Microsoft Windows Server 2008, published on 14 Jul 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A remote code execution vulnerability exists when Hyper-V RemoteFX vGPU on a host server fails to properly validate input from an authenticated user on a guest operating system, aka 'Hyper-V RemoteFX vGPU Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1032, CVE-2020-1036, CVE-2020-1041, CVE-2020-1042, CVE-2020-1043.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 3 products.


Products: Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016.

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

No fix has been published for CVE-2020-1040 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-1040 being exploited?

Yes. Attackers have exploited CVE-2020-1040 in the wild since at least 3 Nov 2021.

## Other vulnerabilities in Microsoft Windows Server 2008

- [CVE-2020-1350](https://insights.sbomify.com/CVE-2020-1350/): Microsoft Windows DNS Server Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2011-1966](https://insights.sbomify.com/CVE-2011-1966/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0239](https://insights.sbomify.com/CVE-2010-0239/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0240](https://insights.sbomify.com/CVE-2010-0240/): Code injection in n/a (critical 10.0)
- [CVE-2010-0241](https://insights.sbomify.com/CVE-2010-0241/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1040 is a critical memory corruption vulnerability in Microsoft Windows Server 2008, published on 14 Jul 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-1040 in the wild since at least 3 Nov 2021.

Affected product: Microsoft Windows Server 2008. 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-1040/ (Markdown: https://insights.sbomify.com/CVE-2020-1040/index.md)
```

## Sources

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

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