CVE-2020-17087
Windows Kernel Local Elevation of Privilege Vulnerability
- CVSS
- 7.8Highscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 3 Nov 2021CISA deadline for US federal agencies: 3 May 2022unvetted proof-of-concept code on github
- EPSS
- 5.4%chance of exploitation in the next 30 daystop 8% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 11 Nov 2020analysed here 12 Nov 2026
Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Microsoft Windows 10 Version 1507 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1607 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1803 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1809 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1903 for 32-bit Systems | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1903 for ARM64-based Systems | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1903 for x64-based Systems | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1909 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 10 Version 2004 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 10 Version 20H2 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 7 | >= 6.1.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 7 Service Pack 1 | >= 6.1.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows 8.1 | >= 6.3.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2008 R2 Service Pack 1 | >= 6.1.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) | >= 6.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 | >= 6.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 | >= 6.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) | >= 6.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2012 | >= 6.2.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 | >= 6.3.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 (Server Core installation) | >= 6.3.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2012 (Server Core installation) | >= 6.2.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2016 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2016 (Server Core installation) | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2019 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server 2019 (Server Core installation) | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server, version 1903 (Server Core installation) | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server, version 1909 (Server Core installation) | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server version 2004 | >= 10.0.0 and < publicationVendor says fixed in: not stated | |
| Microsoft Windows Server version 20H2 | >= 10.0.0 and < publicationVendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- microsoft:windows_10_1507
- microsoft:windows_10_1607
- microsoft:windows_10_1803
- microsoft:windows_10_1809
- microsoft:windows_10_1903
- microsoft:windows_10_1909
- microsoft:windows_10_2004
- microsoft:windows_10_20h2
- microsoft:windows_7
- microsoft:windows_8.1
- microsoft:windows_rt_8.1
- microsoft:windows_server_2008
- microsoft:windows_server_2012
- microsoft:windows_server_2016
- microsoft:windows_server_2019
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 3 Nov 2021.
- CISA due date
- 3 May 2022, the remediation deadline for US federal agencies
- CISA required action
- Apply updates per vendor instructions.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 3 GitHub proofs of concept
- CISA SSVC
- exploitation active, automatable no, technical impact totalAssessed by CISA 30 Jan 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- revengsh/CVE-2020-170874 stars
- ykg88/OHTS_IE6052-CVE-2020-170870 stars
- raiden757/CVE-2020-170870 stars
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 11 Nov 2020Published
- 26 Nov 2020First proof-of-concept repository on GitHub (unvetted)15 days later
- 3 Nov 2021Added to CISA KEV (exploited in the wild)342 days (about 11 months) later
- 3 May 2022CISA remediation due date (US federal agencies)181 days (about 6 months) later
- 30 Jan 2024CISA SSVC assessment: exploitation active638 days (about 2 years) later
- 21 Oct 2025CVE record last updated630 days (about 2 years) later
- 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | LocalLocal access required (shell, logged-in user). | Local access required (shell, logged-in user). |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | LowThe attacker needs basic user privileges. | The attacker needs basic user privileges. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2020-17087 being exploited?
Yes. CVE-2020-17087 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2020-17087?
CVE-2020-17087 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2020-17087?
Yes. A fix has been recorded for CVE-2020-17087. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2020-17087 affect?
CVE-2020-17087 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1803, microsoft:windows_10_1809, and 11 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
2 references in the CVE record, grouped by the tags the record gives them.
Other links (2)
- portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2020-17087
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-17087
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.