Skip to content
Fencer Vulns
high 7.8

CVE-2021-28310 kev in the critical feed json

Win32k Elevation of Privilege Vulnerability

published 2021-04-13 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-14995

cvss
7.8
version 3.1, CNA
cisa kev
Exploited
added 2021-11-03
epss
8.4%
EPSS 8.4% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Win32k Elevation of Privilege Vulnerability

Patch / fix

cisa required action Apply updates per vendor instructions.

Timeline

  1. 0-day patched (Project Zero)
  2. Published
  3. Added to CISA KEV
  4. CISA patch deadline
  5. CISA SSVC: exploitation active

Known exploited

Added
5 y ago
Patch by
2021-11-17 (4 y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Microsoft, Win32k
CISA name
Microsoft Win32k Privilege Escalation Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Patched
2021-04-13
Details
project zero tracker

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

8.40% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Microsoft Windows 10 Version 1803
  • Microsoft Windows 10 Version 1809
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2019 (Server Core installation)
  • Microsoft Windows 10 Version 1909
  • Microsoft Windows Server, version 1909 (Server Core installation)
  • Microsoft Windows 10 Version 2004
  • Microsoft Windows Server version 2004
  • Microsoft Windows 10 Version 20H2
  • Microsoft Windows Server version 20H2

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.