No exploitation reportedFix available

CVE-2020-16913

No exploitation reported by the sources we read.

Published2020-10-16

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

An elevation of privilege vulnerability exists in Windows when the Windows kernel-mode driver fails to properly handle objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. The update addresses this vulnerability by correcting how the Windows kernel-mode driver handles objects in memory.

Timeline

dates in UTC

2020-10-1623:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-16913?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-16913?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Microsoft windows 10

Branch	Affected	Fixed in	Source
1709.x	= 1709	no fix published	NVD
1803.x	= 1803	no fix published	NVD
1809.x	= 1809	no fix published	NVD
1903.x	= 1903	no fix published	NVD
1909.x	= 1909	no fix published	NVD
2004.x	= 2004	no fix published	NVD

Microsoft windows server 2016

Branch	Affected	Fixed in	Source
1903.x	= 1903	no fix published	NVD
1909.x	= 1909	no fix published	NVD
2004.x	= 2004	no fix published	NVD

Microsoft windows server 2019

Branch	Affected	Fixed in	Source
—	all versions	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

portal.msrc.microsoft.comPatch · Vendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

CNACVSS 3.17.8read 2026-10-23
NVDCVSS 3.17.8read 2026-10-23
NVDCVSS 2.07.2read 2026-10-23
FIRST EPSSEPSS score1.0 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published: 2020-10-16
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2020-16913?

Is CVE-2020-16913 actively exploited?

Active exploitation of CVE-2020-16913 has not been confirmed. Its EPSS score was 1.0% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-16913?

CVE-2020-16913 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database