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'.
CVE-2019-1132
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-15), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
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 computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 10%
- EPSS %ILE
- 95%
- KEV
- ⚠ Exploited
Published
July 15, 2019
Last Modified
October 29, 2025
Advisory Details (2)
Auto-updated Jun 3, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1132Security 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-2019-1132All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 89× in last 7d / 338× 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 1,000 total refreshes for this CVE.
- 2026-08-21 23:45 UTCEPSS rescore
- 2026-08-21 21:15 UTCGHSA enrichment
- 2026-08-21 16:51 UTCGHSA enrichment
- 2026-08-21 16:49 UTCCISA KEV update
- 2026-08-21 12:27 UTCVendor advisory
- 2026-08-21 12:27 UTCGHSA enrichment
- 2026-08-21 08:04 UTCVendor advisory
- 2026-08-21 08:04 UTCGHSA enrichment
- 2026-08-21 03:40 UTCVendor advisory
- 2026-08-21 03:40 UTCGHSA enrichment
- 2026-08-20 23:16 UTCEG score recompute
- 2026-08-20 23:16 UTCVendor advisory
- 2026-08-20 23:16 UTCGHSA enrichment
- 2026-08-20 22:51 UTCEPSS rescore
- 2026-08-20 18:53 UTCVendor advisory
- 2026-08-20 18:53 UTCGHSA enrichment
- 2026-08-20 17:06 UTCCISA KEV update
- 2026-08-20 14:30 UTCVendor advisory
- 2026-08-20 14:30 UTCGHSA enrichment
- 2026-08-20 10:06 UTCVendor advisory
- 2026-08-20 10:06 UTCGHSA enrichment
- 2026-08-20 05:43 UTCGHSA enrichment
- 2026-08-20 01:19 UTCGHSA enrichment
- 2026-08-19 20:55 UTCEG score recompute
- 2026-08-19 20:55 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-19 20:55 UTCGHSA enrichment
- 2026-08-19 17:33 UTCCISA KEV update
- 2026-08-19 17:00 UTCEPSS rescore
- 2026-08-19 16:28 UTCVendor advisory
- 2026-08-19 16:28 UTCGHSA enrichment
- 2026-08-19 12:05 UTCVendor advisory
- 2026-08-19 12:04 UTCGHSA enrichment
- 2026-08-19 07:41 UTCVendor advisory
- 2026-08-19 07:41 UTCGHSA enrichment
- 2026-08-19 03:18 UTCVendor advisory
- 2026-08-19 03:18 UTCGHSA enrichment
- 2026-08-18 22:54 UTCGHSA enrichment
- 2026-08-18 18:31 UTCVendor advisory
- 2026-08-18 18:31 UTCGHSA enrichment
- 2026-08-18 16:58 UTCCISA KEV update
- 2026-08-18 14:07 UTCEG score recompute
- 2026-08-18 14:07 UTCVendor advisory
- 2026-08-18 14:07 UTCGHSA enrichment
- 2026-08-18 13:44 UTCEPSS rescore
- 2026-08-18 09:43 UTCGHSA enrichment
- 2026-08-18 05:18 UTCGHSA enrichment
- 2026-08-18 00:52 UTCVendor advisory
- 2026-08-18 00:51 UTCGHSA enrichment
- 2026-08-17 20:25 UTCVendor advisory
- 2026-08-17 20:25 UTCGHSA enrichment
- 2026-08-17 16:02 UTCEG score recompute
- 2026-08-17 16:02 UTCVendor advisory
- 2026-08-17 16:02 UTCGHSA enrichment
- 2026-08-17 13:56 UTCCISA KEV update
- 2026-08-17 13:43 UTCEPSS rescore
- 2026-08-17 11:38 UTCVendor advisory
- 2026-08-17 11:38 UTCGHSA enrichment
- 2026-08-17 07:13 UTCVendor advisory
- 2026-08-17 07:13 UTCGHSA enrichment
- 2026-08-17 02:50 UTCVendor advisory
- 2026-08-17 02:50 UTCGHSA enrichment
- 2026-08-16 22:27 UTCVendor advisory
- 2026-08-16 22:27 UTCGHSA enrichment
- 2026-08-16 18:04 UTCEG score recompute
- 2026-08-16 18:04 UTCVendor advisory
- 2026-08-16 18:04 UTCGHSA enrichment
- 2026-08-16 14:52 UTCEPSS rescore
- 2026-08-16 13:40 UTCVendor advisory
- 2026-08-16 13:40 UTCGHSA enrichment
- 2026-08-16 09:17 UTCVendor advisory
- 2026-08-16 09:17 UTCGHSA enrichment
- 2026-08-16 04:54 UTCEG score recompute
- 2026-08-16 04:54 UTCVendor advisory
- 2026-08-16 04:54 UTCGHSA enrichment
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-16 00:31 UTCVendor advisory
- 2026-08-16 00:31 UTCGHSA enrichment
- 2026-08-15 20:08 UTCVendor advisory
- 2026-08-15 20:08 UTCGHSA enrichment
- 2026-08-15 15:45 UTCVendor advisory
- 2026-08-15 15:45 UTCGHSA enrichment
- 2026-08-15 11:22 UTCVendor advisory
- 2026-08-15 11:22 UTCGHSA enrichment
- 2026-08-15 06:59 UTCVendor advisory
- 2026-08-15 06:59 UTCGHSA enrichment
- 2026-08-15 02:35 UTCEG score recompute
- 2026-08-15 02:35 UTCVendor advisory
- 2026-08-15 02:35 UTCGHSA enrichment
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-14 22:12 UTCVendor advisory
- 2026-08-14 22:12 UTCGHSA enrichment
- 2026-08-14 17:49 UTCVendor advisory
- 2026-08-14 17:49 UTCGHSA enrichment
- 2026-08-14 13:26 UTCVendor advisory
- 2026-08-14 13:26 UTCGHSA enrichment
- 2026-08-14 09:03 UTCGHSA enrichment
- 2026-08-14 04:40 UTCVendor advisory
- 2026-08-14 04:40 UTCGHSA enrichment
- 2026-08-14 00:17 UTCEG score recompute
- 2026-08-14 00:17 UTCVendor advisory
Publicly available exploits
(3 references)Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCpetercc/CVE-2019-1132First seen Jul 31, 2019
CVE-2019-1132
Open source ↗ - Exploit-DBEDB-47176First seen Jul 26, 2019
Microsoft Windows 7 build 7601 (x86) - Local Privilege Escalation
Open source ↗ - GitHub PoCVlad-tri/CVE-2019-1132First seen Jul 26, 2019
EoP POC for CVE-2019-1132
Open source ↗
Related CVEs(same vendor)
Same vendor
10 shownmsrc
Frequently asked(6)
What is CVE-2019-1132?
When was CVE-2019-1132 disclosed?
Is CVE-2019-1132 actively exploited?
What is the CVSS score of CVE-2019-1132?
Which products are affected by CVE-2019-1132?
How do I remediate CVE-2019-1132?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2019-1132
Is Your Infrastructure Affected by CVE-2019-1132?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.