Skip to content
Fencer Vulns
high 7.8

CVE-2019-1132 kev in the critical feed json

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka 'Win32k…

published 2019-07-15 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-9708

cvss
7.8
version 3.1, CNA
cisa kev
Exploited
added 2022-03-15
epss
9.9%
EPSS 9.9% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka '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. First public exploit (EDB-47176)
  4. Added to CISA KEV
  5. CISA patch deadline
  6. CISA SSVC: exploitation active

Known exploited

Added
4 y ago
Patch by
2022-04-05 (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
2019-07-09
Details
project zero tracker

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
21 mo ago

Exploit prediction

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

Exploits and checks

  • EDB-47176 Microsoft Windows 7 build 7601 (x86) - Local Privilege Escalation local, 2019-07-26

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • Microsoft Windows
  • Microsoft Windows Server

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.