Live › vulnerability › CVE-2020-1054
Go to dashboardMicrosoft Win32k, the Windows kernel-mode graphics driver, mishandles objects in memory. An attacker who already runs code on the machine can escalate to kernel-mode code execution, which gives full control of the system.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply updates per vendor instructions.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Microsoft Win32k | vendor | – | – |
Unknown from the sources. In the analyst’s queue.
Apply the Microsoft security update for CVE-2020-1054 per vendor instructions (CISA KEV required action); the sources do not name the patched build.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2020-1054")
CISA KEV catalog, Creative Commons 0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.