CVE-2019-1184

HIGHNVD 6.78.7
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 8.7 because EPSS predicted 70% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 6.7 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated
8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 70%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 70%CVSS: 6.7Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

An elevation of privilege vulnerability exists when Windows Core Shell COM Server Registrar improperly handles COM calls. An attacker who successfully exploited this vulnerability could potentially set certain items to run at a higher level and thereby elevate permissions. To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. The update addresses this vulnerability by correcting unprotected COM calls.

CVSS v3
6.7
EG Score
8.7HIGHhigh confidence
EG Risk
63
EG Risk 63/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation70% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
70%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.8 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
70% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 14, 2019

Last Modified

February 20, 2026

References (1)

Vendor Advisories for CVE-2019-1184(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 9× in last 7d / 22× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 86 of 112 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 14 repeat rows among the latest 100 are merged into the row they repeat. The 26 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-22 16:28 UTCEPSS rescoreEPSS 70% · 99th percentile
  2. 2026-10-21 18:38 UTCEG score recompute
  3. 2026-10-21 18:38 UTCVendor advisory
  4. 2026-10-21 18:37 UTCGHSA enrichmentGHSA-24jg-p7g4-p8rm · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-21 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
  6. 2026-10-20 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
  7. 2026-10-19 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
  8. 2026-10-18 09:56 UTCEG score recompute
  9. 2026-10-17 16:28 UTCEPSS rescoreEPSS 70% · 99th percentile
  10. 2026-10-15 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
  11. 2026-10-14 16:28 UTCEPSS rescoreEPSS 70% · 99th percentile
  12. 2026-10-13 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
  13. 2026-10-12 20:04 UTCEG score recompute
  14. 2026-10-12 16:28 UTCEPSS rescoreEPSS 70% · 99th percentile
  15. 2026-10-12 00:27 UTCEG score recompute
  16. 2026-10-10 19:55 UTCEPSS rescoreEPSS 70% · 99th percentile
  17. 2026-10-07 23:43 UTCEPSS rescoreEPSS 70% · 99th percentile
  18. 2026-10-06 15:12 UTCEPSS rescoreEPSS 70% · 99th percentile
  19. 2026-09-30 10:09 UTCEG score recompute
  20. 2026-09-26 15:54 UTCEPSS rescoreEPSS 70% · 99th percentile
  21. 2026-09-24 13:59 UTCEPSS rescoreEPSS 70% · 99th percentile
  22. 2026-09-23 13:43 UTCEPSS rescoreEPSS 70% · 99th percentile
  23. 2026-09-22 14:43 UTCEPSS rescoreEPSS 70% · 99th percentile
  24. 2026-09-21 20:28 UTCEPSS rescoreEPSS 70% · 99th percentile
  25. 2026-09-20 20:10 UTCEPSS rescoreEPSS 70% · 99th percentile
Show 61 more
  1. 2026-09-18 19:22 UTCEPSS rescoreEPSS 70% · 99th percentile
  2. 2026-09-17 19:22 UTCEPSS rescoreEPSS 70% · 99th percentile
  3. 2026-09-16 14:04 UTCEPSS rescoreEPSS 70% · 99th percentile
  4. 2026-09-15 03:05 UTCEPSS rescoreEPSS 70% · 99th percentile
  5. 2026-09-12 14:56 UTCEPSS rescoreEPSS 70% · 99th percentile
  6. 2026-09-11 14:48 UTCEPSS rescoreEPSS 70% · 99th percentile
  7. 2026-09-11 09:32 UTCEPSS rescoreEPSS 70% · 99th percentile
  8. 2026-09-07 15:57 UTCEPSS rescoreEPSS 70% · 99th percentile
  9. 2026-09-06 13:44 UTCEPSS rescoreEPSS 70% · 99th percentile
  10. 2026-09-05 15:24 UTCEPSS rescoreEPSS 70% · 99th percentile
  11. 2026-09-04 13:56 UTCEPSS rescoreEPSS 70% · 99th percentile
  12. 2026-09-02 14:07 UTCEPSS rescoreEPSS 70% · 99th percentile
  13. 2026-08-30 19:13 UTCEPSS rescoreEPSS 70% · 99th percentile
  14. 2026-08-30 01:18 UTCEPSS rescoreEPSS 70% · 99th percentile
  15. 2026-08-28 21:36 UTCEPSS rescoreEPSS 70% · 99th percentile
  16. 2026-08-26 14:42 UTCEPSS rescoreEPSS 70% · 99th percentile
  17. 2026-08-25 13:45 UTCEPSS rescoreEPSS 70% · 99th percentile
  18. 2026-08-24 14:11 UTCEPSS rescoreEPSS 70% · 99th percentile
  19. 2026-08-20 22:51 UTCEPSS rescoreEPSS 70% · 99th percentile
  20. 2026-08-19 17:00 UTCEPSS rescoreEPSS 70% · 99th percentile
  21. 2026-08-16 14:52 UTCEPSS rescoreEPSS 70% · 99th percentile
  22. 2026-08-16 02:10 UTCEPSS rescoreEPSS 70% · 99th percentile
  23. 2026-08-15 01:26 UTCEPSS rescoreEPSS 70% · 99th percentile
  24. 2026-08-12 13:47 UTCEPSS rescoreEPSS 70% · 99th percentile
  25. 2026-08-07 16:23 UTCEPSS rescoreEPSS 70% · 99th percentile
  26. 2026-08-05 19:13 UTCEPSS rescoreEPSS 70% · 99th percentile
  27. 2026-08-01 04:12 UTCEPSS rescoreEPSS 70% · 99th percentile
  28. 2026-07-30 16:24 UTCEPSS rescoreEPSS 70% · 99th percentile
  29. 2026-07-28 15:32 UTCEPSS rescoreEPSS 70% · 99th percentile
  30. 2026-07-26 14:51 UTCEPSS rescoreEPSS 70% · 99th percentile
  31. 2026-07-24 14:14 UTCEPSS rescoreEPSS 70% · 99th percentile
  32. 2026-07-23 01:39 UTCEG score recompute▲ 0.90
  33. 2026-07-22 22:19 UTCEG score recompute
  34. 2026-07-22 14:05 UTCEPSS rescoreEPSS 70% · 99th percentile
  35. 2026-07-21 15:22 UTCEPSS rescoreEPSS 70% · 99th percentile
  36. 2026-07-20 17:04 UTCEPSS rescoreEPSS 70% · 99th percentile
  37. 2026-07-16 16:59 UTCEPSS rescoreEPSS 70% · 99th percentile
  38. 2026-07-15 16:55 UTCEPSS rescoreEPSS 70% · 99th percentile
  39. 2026-07-13 22:27 UTCEPSS rescoreEPSS 70% · 99th percentile
  40. 2026-07-11 08:24 UTCEPSS rescoreEPSS 70% · 99th percentile
  41. 2026-07-09 19:06 UTCEPSS rescoreEPSS 70% · 99th percentile
  42. 2026-07-05 02:27 UTCEPSS rescoreEPSS 70% · 99th percentile
  43. 2026-07-01 15:03 UTCEPSS rescoreEPSS 70% · 99th percentile
  44. 2026-06-27 03:06 UTCEPSS rescoreEPSS 70% · 99th percentile
  45. 2026-06-25 13:47 UTCEPSS rescoreEPSS 70% · 99th percentile
  46. 2026-06-24 14:03 UTCEPSS rescoreEPSS 70% · 99th percentile
  47. 2026-06-23 21:30 UTCEPSS rescoreEPSS 70% · 99th percentile
  48. 2026-06-22 14:23 UTCEPSS rescoreEPSS 70% · 99th percentile
  49. 2026-06-21 14:54 UTCEPSS rescoreEPSS 70% · 99th percentile
  50. 2026-06-17 17:50 UTCEPSS rescoreEPSS 70% · 99th percentile
  51. 2026-06-16 17:50 UTCEPSS rescoreEPSS 70% · 99th percentile
  52. 2026-06-15 17:45 UTCEPSS rescoreEPSS 70% · 99th percentile
  53. 2026-06-14 23:15 UTCEPSS rescoreEPSS 7.3% · 91st percentile
  54. 2026-06-13 22:58 UTCEPSS rescoreEPSS 7.3% · 91st percentile
  55. 2026-06-12 23:09 UTCEPSS rescoreEPSS 7.3% · 91st percentile
  56. 2026-06-11 13:58 UTCEPSS rescoreEPSS 7.3% · 91st percentile
  57. 2026-06-10 22:16 UTCEPSS rescoreEPSS 7.3% · 91st percentile
  58. 2026-06-10 13:19 UTCEPSS rescoreEPSS 7.3% · 91st percentile
  59. 2026-06-08 14:15 UTCEPSS rescoreEPSS 7.3% · 91st percentile
  60. 2026-06-07 15:23 UTCEPSS rescoreEPSS 7.3% · 91st percentile
  61. 2026-06-06 13:45 UTCEPSS rescoreEPSS 7.3% · 91st percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-47880
    Published Jan 2, 2020

    Microsoft Windows - Shell COM Server Registrar Local Privilege Escalation

    Open source ↗

Frequently asked(5)

What is CVE-2019-1184?
CVE-2019-1184 is a high-severity vulnerability; its CVE record was published on August 14, 2019. An elevation of privilege vulnerability exists when Windows Core Shell COM Server Registrar improperly handles COM calls. An attacker who successfully exploited this vulnerability could potentially set certain items to run at a higher level and thereby elevate permissions. To exploit this…
When was CVE-2019-1184 made public?
CVE-2019-1184 was made public on August 13, 2019: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on August 14, 2019. EchelonGraph's copy of the record carries a last-modified date of February 20, 2026; the record at its source may have been updated since.
Is CVE-2019-1184 actively exploited?
CVE-2019-1184 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 70% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-1184?
CVE-2019-1184 has a CVSS v3 base score of 6.7 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.7 (HIGH).
How do I remediate CVE-2019-1184?
A fix for CVE-2019-1184 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-1184 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2019-1184?

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

Book a Demo →Browse All CVEs