CVE-2019-0903 Microsoft GDI Remote Code Execution Vulnerability
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.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 25 Mar 2022.
- Rated High severity (CVSS 8.8, scored by CISA).
- It has been in the catalogue for 1,687 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
A remote code execution vulnerability exists in the way that the Windows Graphics Device Interface (GDI) handles objects in the memory, aka 'GDI+ Remote Code Execution Vulnerability'.
Affected Versions
| Product | Versions |
|---|---|
| Microsoft Windows | 7 for 32-bit Systems Service Pack 1 7 for x64-based Systems Service Pack 1 8.1 for 32-bit systems 8.1 for x64-based systems RT 8.1 10 for 32-bit Systems |
| Microsoft Windows Server | 2008 R2 for x64-based Systems Service Pack 1 (Core installation) 2008 R2 for Itanium-Based Systems Service Pack 1 2008 R2 for x64-based Systems Service Pack 1 2008 for 32-bit Systems Service Pack 2 (Core installation) 2012 2012 (Core installation) |
| Microsoft Windows 10 Version 1903 for 32-bit Systems | unspecified |
| Microsoft Windows 10 Version 1903 for x64-based Systems | unspecified |
| Microsoft Windows 10 Version 1903 for ARM64-based Systems | unspecified |
| Microsoft Windows Server, version 1903 (Server Core installation) | unspecified |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Microsoft Graphics Device Interface (GDI). Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
- 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
Vendor Advisories
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2019-0903 and every other exploited flaw on the list.