CVE-2019-0859

HIGHNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 4%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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'. This CVE ID is unique from CVE-2019-0685, CVE-2019-0803.

CVSS v3
7.8
EG Score
9.0(high)
EPSS
89.6%
KEV
⚠ Exploited

Published

April 9, 2019

Last Modified

October 29, 2025

Advisory Details (2)

Auto-updated Jun 4, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft, cisa.
cisa Patch Available🔴 Active Exploitation

Known 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-0859
microsoft Patch Available

Security 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-0859

All 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 131× in last 7d / 544× 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 685 total refreshes for this CVE.

  1. 2026-07-07 11:48 UTCEG score recompute
  2. 2026-07-07 11:48 UTCVendor advisory
  3. 2026-07-07 11:48 UTCGHSA enrichment
  4. 2026-07-07 07:32 UTCEG score recompute
  5. 2026-07-07 07:32 UTCVendor advisory
  6. 2026-07-07 07:32 UTCGHSA enrichment
  7. 2026-07-07 03:13 UTCEG score recompute
  8. 2026-07-07 03:13 UTCVendor advisory
  9. 2026-07-07 03:13 UTCGHSA enrichment
  10. 2026-07-06 22:57 UTCEG score recompute
  11. 2026-07-06 22:57 UTCVendor advisory
  12. 2026-07-06 22:57 UTCGHSA enrichment
  13. 2026-07-06 18:40 UTCEG score recompute
  14. 2026-07-06 18:40 UTCVendor advisory
  15. 2026-07-06 18:39 UTCGHSA enrichment
  16. 2026-07-06 16:25 UTCEPSS rescore
  17. 2026-07-06 16:24 UTCEPSS rescore
  18. 2026-07-06 14:22 UTCEG score recompute
  19. 2026-07-06 14:22 UTCVendor advisory
  20. 2026-07-06 14:22 UTCGHSA enrichment
  21. 2026-07-06 10:06 UTCEG score recompute
  22. 2026-07-06 10:06 UTCVendor advisory
  23. 2026-07-06 10:06 UTCGHSA enrichment
  24. 2026-07-06 05:49 UTCEG score recompute
  25. 2026-07-06 05:49 UTCVendor advisory
Show 75 more
  1. 2026-07-06 05:49 UTCGHSA enrichment
  2. 2026-07-06 02:20 UTCEPSS rescore
  3. 2026-07-06 01:31 UTCEG score recompute
  4. 2026-07-06 01:31 UTCVendor advisory
  5. 2026-07-06 01:31 UTCGHSA enrichment
  6. 2026-07-05 21:15 UTCEG score recompute
  7. 2026-07-05 21:15 UTCVendor advisory
  8. 2026-07-05 21:15 UTCGHSA enrichment
  9. 2026-07-05 16:59 UTCEG score recompute
  10. 2026-07-05 16:59 UTCVendor advisory
  11. 2026-07-05 16:59 UTCGHSA enrichment
  12. 2026-07-05 12:43 UTCEG score recompute
  13. 2026-07-05 12:43 UTCVendor advisory
  14. 2026-07-05 12:43 UTCGHSA enrichment
  15. 2026-07-05 08:24 UTCEG score recompute
  16. 2026-07-05 08:24 UTCVendor advisory
  17. 2026-07-05 08:24 UTCGHSA enrichment
  18. 2026-07-05 04:07 UTCEG score recompute
  19. 2026-07-05 04:07 UTCVendor advisory
  20. 2026-07-05 04:07 UTCGHSA enrichment
  21. 2026-07-05 02:27 UTCEPSS rescore
  22. 2026-07-04 23:51 UTCEG score recompute
  23. 2026-07-04 23:51 UTCVendor advisory
  24. 2026-07-04 23:51 UTCGHSA enrichment
  25. 2026-07-04 19:35 UTCEG score recompute
  26. 2026-07-04 19:35 UTCVendor advisory
  27. 2026-07-04 19:35 UTCGHSA enrichment
  28. 2026-07-04 15:19 UTCEG score recompute
  29. 2026-07-04 15:19 UTCVendor advisory
  30. 2026-07-04 15:18 UTCGHSA enrichment
  31. 2026-07-04 11:02 UTCEG score recompute
  32. 2026-07-04 11:02 UTCVendor advisory
  33. 2026-07-04 11:02 UTCGHSA enrichment
  34. 2026-07-04 06:46 UTCEG score recompute
  35. 2026-07-04 06:46 UTCVendor advisory
  36. 2026-07-04 06:46 UTCGHSA enrichment
  37. 2026-07-04 06:28 UTCEPSS rescore
  38. 2026-07-04 06:28 UTCEPSS rescore
  39. 2026-07-04 02:29 UTCEG score recompute
  40. 2026-07-04 02:29 UTCVendor advisory
  41. 2026-07-04 02:29 UTCGHSA enrichment
  42. 2026-07-03 22:10 UTCEG score recompute
  43. 2026-07-03 22:10 UTCVendor advisory
  44. 2026-07-03 22:10 UTCGHSA enrichment
  45. 2026-07-03 17:54 UTCEG score recompute
  46. 2026-07-03 17:54 UTCVendor advisory
  47. 2026-07-03 17:54 UTCGHSA enrichment
  48. 2026-07-03 13:37 UTCEG score recompute
  49. 2026-07-03 13:37 UTCVendor advisory
  50. 2026-07-03 13:37 UTCGHSA enrichment
  51. 2026-07-03 09:21 UTCEG score recompute
  52. 2026-07-03 09:21 UTCVendor advisory
  53. 2026-07-03 09:21 UTCGHSA enrichment
  54. 2026-07-03 05:05 UTCEG score recompute
  55. 2026-07-03 05:05 UTCVendor advisory
  56. 2026-07-03 05:05 UTCGHSA enrichment
  57. 2026-07-03 00:48 UTCEG score recompute
  58. 2026-07-03 00:48 UTCVendor advisory
  59. 2026-07-03 00:48 UTCGHSA enrichment
  60. 2026-07-02 20:32 UTCEG score recompute
  61. 2026-07-02 20:32 UTCVendor advisory
  62. 2026-07-02 20:32 UTCGHSA enrichment
  63. 2026-07-02 16:16 UTCEG score recompute
  64. 2026-07-02 16:16 UTCVendor advisory
  65. 2026-07-02 16:16 UTCGHSA enrichment
  66. 2026-07-02 12:00 UTCEG score recompute
  67. 2026-07-02 12:00 UTCVendor advisory
  68. 2026-07-02 12:00 UTCGHSA enrichment
  69. 2026-07-02 07:43 UTCEG score recompute
  70. 2026-07-02 07:43 UTCVendor advisory
  71. 2026-07-02 07:43 UTCGHSA enrichment
  72. 2026-07-02 03:27 UTCEG score recompute
  73. 2026-07-02 03:27 UTCVendor advisory
  74. 2026-07-02 03:27 UTCGHSA enrichment
  75. 2026-07-01 23:10 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCSheisback/CVE-2019-0859-1day-Exploit
    First seen Jun 7, 2019

    CVE-2019-0859 1day Exploit

    Open source ↗

Related CVEs(same vendor)

Frequently asked(6)

What is CVE-2019-0859?
CVE-2019-0859 is a high vulnerability published on April 9, 2019. 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'. This CVE ID is unique from CVE-2019-0685, CVE-2019-0803.
When was CVE-2019-0859 disclosed?
CVE-2019-0859 was first published in the National Vulnerability Database on April 9, 2019, with the most recent update on October 29, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0859 actively exploited?
Yes. CISA added CVE-2019-0859 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Win32k. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2019-0859?
CVE-2019-0859 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2019-0859?
CVE-2019-0859 affects Microsoft Win32k. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2019-0859?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0859, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-0859

Explore →

Is Your Infrastructure Affected by CVE-2019-0859?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs