CVE-2019-0863

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: 5%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 the way Windows Error Reporting (WER) handles files, aka 'Windows Error Reporting Elevation of Privilege Vulnerability'.

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

Published

May 16, 2019

Last Modified

October 29, 2025

Advisory Details (3)

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-0863
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-0863

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 133× in last 7d / 556× 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 723 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-46917
    First seen May 22, 2019

    Microsoft Windows (x86/x64) - 'Error Reporting' Discretionary Access Control List / Local Privilege Escalation

    Open source ↗

Frequently asked(6)

What is CVE-2019-0863?
CVE-2019-0863 is a high vulnerability published on May 16, 2019. An elevation of privilege vulnerability exists in the way Windows Error Reporting (WER) handles files, aka 'Windows Error Reporting Elevation of Privilege Vulnerability'.
When was CVE-2019-0863 disclosed?
CVE-2019-0863 was first published in the National Vulnerability Database on May 16, 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-0863 actively exploited?
Yes. CISA added CVE-2019-0863 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2019-0863?
CVE-2019-0863 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-0863?
CVE-2019-0863 affects Microsoft Windows. 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-0863?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0863, 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-0863

Explore →

Is Your Infrastructure Affected by CVE-2019-0863?

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