CVE-2020-16911

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A remote code execution vulnerability exists in the way that the Windows Graphics Device Interface (GDI) handles objects in the memory. An attacker who successfully exploited this vulnerability could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. There are multiple ways an attacker could exploit the vulnerability:

In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability and then convince users to view the website. An attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by getting them to open an email attachment or click a link in an email or instant message. In a file-sharing attack scenario, an attacker could provide a specially crafted document file that is designed to exploit the vulnerability, and then convince users to open the document file.

The security update addresses the vulnerability by correcting the way that the Windows GDI handles objects in the memory.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
46
EG Risk 46/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation4% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
4.5%
EPSS %ILE
91st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 16, 2020

Last Modified

February 23, 2026

Advisory Details (1)

Auto-updated Aug 9, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-16911

Vendor Advisories for CVE-2020-16911(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 6× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 157 total refreshes for this CVE.

  1. 2026-10-05 17:39 UTCEPSS rescore
  2. 2026-10-04 23:18 UTCEPSS rescore
  3. 2026-10-03 14:22 UTCEPSS rescore
  4. 2026-10-02 16:22 UTCEPSS rescore
  5. 2026-09-30 15:13 UTCEG score recompute
  6. 2026-09-30 14:59 UTCEPSS rescore
  7. 2026-09-27 13:40 UTCEPSS rescore
  8. 2026-09-26 15:54 UTCEPSS rescore
  9. 2026-09-26 00:20 UTCEPSS rescore
  10. 2026-09-24 14:00 UTCEPSS rescore
  11. 2026-09-24 14:00 UTCEPSS rescore
  12. 2026-09-22 14:43 UTCEPSS rescore
  13. 2026-09-21 20:28 UTCEPSS rescore
  14. 2026-09-20 20:11 UTCEPSS rescore
  15. 2026-09-18 19:23 UTCEPSS rescore
  16. 2026-09-17 19:22 UTCEPSS rescore
  17. 2026-09-17 19:22 UTCEPSS rescore
  18. 2026-09-16 14:04 UTCEPSS rescore
  19. 2026-09-15 03:06 UTCEPSS rescore
  20. 2026-09-15 03:06 UTCEPSS rescore
  21. 2026-09-12 14:56 UTCEPSS rescore
  22. 2026-09-11 14:48 UTCEPSS rescore
  23. 2026-09-11 09:32 UTCEPSS rescore
  24. 2026-09-10 09:29 UTCEPSS rescore
  25. 2026-09-08 21:56 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 15:57 UTCEPSS rescore
  2. 2026-09-06 13:44 UTCEPSS rescore
  3. 2026-09-05 15:24 UTCEPSS rescore
  4. 2026-09-04 13:57 UTCEPSS rescore
  5. 2026-09-04 05:03 UTCEPSS rescore
  6. 2026-09-02 14:08 UTCEPSS rescore
  7. 2026-09-01 03:32 UTCEPSS rescore
  8. 2026-08-30 19:14 UTCEPSS rescore
  9. 2026-08-30 01:18 UTCEPSS rescore
  10. 2026-08-27 14:21 UTCEPSS rescore
  11. 2026-08-26 14:42 UTCEPSS rescore
  12. 2026-08-25 13:45 UTCEPSS rescore
  13. 2026-08-21 23:45 UTCEPSS rescore
  14. 2026-08-20 22:52 UTCEPSS rescore
  15. 2026-08-19 17:00 UTCEPSS rescore
  16. 2026-08-18 13:44 UTCEPSS rescore
  17. 2026-08-17 13:43 UTCEPSS rescore
  18. 2026-08-16 14:52 UTCEPSS rescore
  19. 2026-08-16 02:11 UTCEPSS rescore
  20. 2026-08-15 01:26 UTCEPSS rescore
  21. 2026-08-13 21:57 UTCEPSS rescore
  22. 2026-08-12 13:47 UTCEPSS rescore
  23. 2026-08-09 13:43 UTCEPSS rescore
  24. 2026-08-08 16:33 UTCEPSS rescore
  25. 2026-08-07 16:23 UTCEPSS rescore
  26. 2026-08-06 13:43 UTCEPSS rescore
  27. 2026-08-05 19:14 UTCEPSS rescore
  28. 2026-08-04 15:06 UTCEPSS rescore
  29. 2026-08-04 10:34 UTCEPSS rescore
  30. 2026-08-03 10:32 UTCEPSS rescore
  31. 2026-08-02 02:23 UTCEPSS rescore
  32. 2026-08-01 04:12 UTCEPSS rescore
  33. 2026-07-30 16:25 UTCEPSS rescore
  34. 2026-07-30 01:27 UTCEPSS rescore
  35. 2026-07-28 15:32 UTCEPSS rescore
  36. 2026-07-27 14:06 UTCEPSS rescore
  37. 2026-07-25 14:15 UTCEPSS rescore
  38. 2026-07-25 14:14 UTCEPSS rescore
  39. 2026-07-24 14:14 UTCEPSS rescore
  40. 2026-07-23 14:15 UTCEPSS rescore
  41. 2026-07-23 14:15 UTCEPSS rescore
  42. 2026-07-23 01:50 UTCEG score recompute
  43. 2026-07-22 22:35 UTCEG score recompute
  44. 2026-07-22 14:05 UTCEPSS rescore
  45. 2026-07-21 15:22 UTCEPSS rescore
  46. 2026-07-21 15:22 UTCEPSS rescore
  47. 2026-07-20 17:04 UTCEPSS rescore
  48. 2026-07-20 17:04 UTCEPSS rescore
  49. 2026-07-19 14:28 UTCEPSS rescore
  50. 2026-07-19 02:26 UTCEPSS rescore
  51. 2026-07-19 02:26 UTCEPSS rescore
  52. 2026-07-18 10:02 UTCEPSS rescore
  53. 2026-07-16 16:59 UTCEPSS rescore
  54. 2026-07-15 16:55 UTCEPSS rescore
  55. 2026-07-15 01:57 UTCEPSS rescore
  56. 2026-07-13 22:27 UTCEPSS rescore
  57. 2026-07-13 22:27 UTCEPSS rescore
  58. 2026-07-13 06:10 UTCEPSS rescore
  59. 2026-07-13 06:10 UTCEPSS rescore
  60. 2026-07-12 05:44 UTCEPSS rescore
  61. 2026-07-11 08:25 UTCEPSS rescore
  62. 2026-07-11 08:25 UTCEPSS rescore
  63. 2026-07-09 19:07 UTCEPSS rescore
  64. 2026-07-08 15:12 UTCEPSS rescore
  65. 2026-07-07 13:43 UTCEPSS rescore
  66. 2026-07-07 13:43 UTCEPSS rescore
  67. 2026-07-06 16:25 UTCEPSS rescore
  68. 2026-07-06 16:25 UTCEPSS rescore
  69. 2026-07-06 02:21 UTCEPSS rescore
  70. 2026-07-06 02:21 UTCEPSS rescore
  71. 2026-07-05 02:27 UTCEPSS rescore
  72. 2026-07-04 06:29 UTCEPSS rescore
  73. 2026-07-04 06:28 UTCEPSS rescore
  74. 2026-07-01 15:03 UTCEPSS rescore
  75. 2026-06-30 23:20 UTCEPSS rescore

Frequently asked(5)

What is CVE-2020-16911?
CVE-2020-16911 is a high vulnerability published on October 16, 2020. <p>A remote code execution vulnerability exists in the way that the Windows Graphics Device Interface (GDI) handles objects in the memory. An attacker who successfully exploited this vulnerability could take control of the affected system. An attacker could then install programs; view, change, or…
When was CVE-2020-16911 disclosed?
CVE-2020-16911 was first published on October 16, 2020, with the most recent update on February 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-16911 actively exploited?
CVE-2020-16911 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.5% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-16911?
CVE-2020-16911 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2020-16911?
A fix for CVE-2020-16911 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-16911 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-16911

Explore →

Is Your Infrastructure Affected by CVE-2020-16911?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.