Microsoft Hyper-V RemoteFX vGPU Remote Code Execution Vulnerability
CVE-2020-1040 is a security vulnerability in Microsoft Hyper-V RemoteFX, added to CISA KEV on November 3, 2021. Patch order: second of four.
What is CVE-2020-1040?
Microsoft Hyper-V RemoteFX vGPU contains an improper input validation vulnerability due to the host server failing to properly validate input from an authenticated user on a guest operating system. Successful exploitation allows for remote code execution on the host operating system.
VulnCheck tracked exploitation 379 days before CISA's KEV listing. VulnCheck's broader catalog of in-the-wild exploitation evidence picked this up before it landed on CISA's formal list. Per-CVE fact about this entry; not a population claim about lead time in general.
Who is affected by CVE-2020-1040?
Affects anyone running Microsoft Hyper-V RemoteFX. Microsoft products in a small practice typically sit close to credentials, email, or document workflows — treat the patch as in-scope.
What should I do about CVE-2020-1040?
Apply updates per vendor instructions.
If you don't have someone in-house to verify the patch deployed across every endpoint — or you're not sure whether you're affected — that's exactly the kind of triage we do. Request a free review.
Insurance readiness
Your insurer will ask if this is patched.
Unpatched entries on CISA's Known Exploited Vulnerabilities list are exactly what cyber-insurance carrier questionnaires probe for, and knowing which controls they check is how you keep a renewal from stalling.
Get the free carrier questionnaire →Severity
CVSS base score: 9.0 — CRITICAL
Weakness classification: CWE-20
Microsoft fix
No fixing KB is published yet in the Microsoft Security Update Guide for this CVE. Check Microsoft's advisory page directly if you need to verify whether an update has shipped.
Microsoft Exploitability Index (assessed at update release): Exploitation Less Likely
This CVE is on CISA's Known Exploited Vulnerabilities catalog. Microsoft's index reflects their release-time forecast, not current observed activity, and is not automatically revised upward when exploitation appears later.
Vendor workaround
No vendor workaround published. Patching is the only fix.
CISA due date
CISA's listed due date: May 3, 2022.
Federal civilian agencies work under CISA's Binding Operational Directive 26-04, which replaced BOD 22-01 on June 10, 2026. It sets the deadline for each affected system by:
- How exposed that system is to the internet
- Whether the attack can be automated
- How much control it gives an attacker
Its table gives catalogued vulnerabilities 3 or 14 days.
None of this binds a private business, but treat the date as a strong recommendation, especially if you handle regulated data (HIPAA, GLBA, ABA model rules).
EPSS
EPSS score: 7.4% — higher than 94% of all scored CVEs.
EPSS estimates the probability of exploitation activity in the next 30 days. Every entry on this site is already confirmed exploited, so read it as relative urgency among the things you still have open, not as permission to wait.
Source
This entry comes from CISA's Known Exploited Vulnerabilities catalog, public US-Government data we pull daily. The plain-language framing and the what-to-do guidance above are ours. View the original entry on cisa.gov.