CVE-2019-1214

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

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

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. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2019-9782 (ENISA EUVD) · GHSA-2q4x-j5p2-9wxv (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 1.4%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

An elevation of privilege vulnerability exists when the Windows Common Log File System (CLFS) driver improperly handles objects in memory, aka 'Windows Common Log File System Driver Elevation of Privilege Vulnerability'.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
75
EG Risk 75/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.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (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 at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
1.4%
EPSS %ILE
73rd
KEV
⚠ Exploited

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

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (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)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (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

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2019-1214

Published

September 11, 2019

Last Modified

October 29, 2025

Advisory Details (2)

Auto-updated Nov 11, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa, microsoft.
CISA🔴 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-1214
Microsoft

Security Update Guide - Microsoft Security Response Center

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1214

Vendor Advisories for CVE-2019-1214(1)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 0× in last 7d / 0× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 23:15 UTCEchelonGraph re-scored
  2. 2026-11-12 23:15 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-11-12 16:28 UTCEPSS rescoreEPSS 1.4% · 73rd percentile
  4. 2026-11-12 00:17 UTCEchelonGraph re-scored
  5. 2026-11-12 00:17 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-11-11 16:30 UTCEPSS rescoreEPSS 1.4% · 73rd percentile
  7. 2026-11-11 01:18 UTCEchelonGraph re-scored
  8. 2026-11-11 01:18 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-11-10 16:33 UTCEPSS rescoreEPSS 1.4% · 73rd percentile
  10. 2026-11-10 02:20 UTCEchelonGraph re-scored
  11. 2026-11-10 02:19 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-11-09 16:28 UTCEPSS rescoreEPSS 1.4% · 73rd percentile
  13. 2026-11-09 03:21 UTCEchelonGraph re-scored
  14. 2026-11-09 03:21 UTCVendor advisory
  15. 2026-11-09 03:21 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-11-08 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  17. 2026-11-08 04:24 UTCEchelonGraph re-scored
  18. 2026-11-08 04:24 UTCVendor advisory
  19. 2026-11-08 04:24 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-11-07 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  21. 2026-11-07 05:22 UTCEchelonGraph re-scored
  22. 2026-11-07 05:22 UTCVendor advisory
  23. 2026-11-07 05:22 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-11-06 16:29 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  25. 2026-11-06 06:24 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-06 06:24 UTCVendor advisory
  2. 2026-11-06 06:24 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-11-05 16:29 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  4. 2026-11-05 07:26 UTCEchelonGraph re-scored
  5. 2026-11-05 07:26 UTCVendor advisory
  6. 2026-11-05 07:26 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-11-04 16:28 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  8. 2026-11-04 08:28 UTCEchelonGraph re-scored
  9. 2026-11-04 08:28 UTCVendor advisory
  10. 2026-11-04 08:28 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-11-03 16:35 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  12. 2026-11-03 09:30 UTCEchelonGraph re-scored
  13. 2026-11-03 09:30 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-11-02 16:35 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  15. 2026-11-02 10:32 UTCEchelonGraph re-scored
  16. 2026-11-02 10:32 UTCVendor advisory
  17. 2026-11-02 10:32 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-11-01 16:28 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  19. 2026-11-01 11:34 UTCEchelonGraph re-scored
  20. 2026-11-01 11:34 UTCVendor advisory
  21. 2026-11-01 11:34 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-31 16:28 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  23. 2026-10-31 12:36 UTCEchelonGraph re-scored
  24. 2026-10-31 12:36 UTCVendor advisory
  25. 2026-10-31 12:35 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  26. 2026-10-30 16:29 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  27. 2026-10-30 13:36 UTCEchelonGraph re-scored
  28. 2026-10-30 13:36 UTCVendor advisory
  29. 2026-10-30 13:36 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  30. 2026-10-29 16:28 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  31. 2026-10-29 14:37 UTCEchelonGraph re-scored
  32. 2026-10-29 14:37 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  33. 2026-10-28 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  34. 2026-10-28 15:40 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-10-27 16:42 UTCEchelonGraph re-scored
  36. 2026-10-27 16:42 UTCVendor advisory
  37. 2026-10-27 16:42 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-10-27 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  39. 2026-10-26 17:41 UTCEchelonGraph re-scored
  40. 2026-10-26 17:41 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  41. 2026-10-26 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  42. 2026-10-25 18:42 UTCEchelonGraph re-scored
  43. 2026-10-25 18:42 UTCVendor advisory
  44. 2026-10-25 18:42 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  45. 2026-10-25 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  46. 2026-10-24 19:43 UTCEchelonGraph re-scored
  47. 2026-10-24 19:43 UTCVendor advisory
  48. 2026-10-24 19:43 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  49. 2026-10-24 16:28 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  50. 2026-10-23 20:46 UTCEchelonGraph re-scored
  51. 2026-10-23 20:46 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-10-23 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  53. 2026-10-22 21:47 UTCEchelonGraph re-scored
  54. 2026-10-22 21:47 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-10-22 16:28 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  56. 2026-10-21 22:49 UTCEchelonGraph re-scored
  57. 2026-10-21 22:49 UTCVendor advisory
  58. 2026-10-21 22:49 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-10-21 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  60. 2026-10-20 23:51 UTCEchelonGraph re-scored
  61. 2026-10-20 23:51 UTCVendor advisory
  62. 2026-10-20 23:51 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-10-20 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  64. 2026-10-20 00:50 UTCEchelonGraph re-scored
  65. 2026-10-20 00:50 UTCVendor advisory
  66. 2026-10-20 00:50 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-10-19 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  68. 2026-10-19 01:52 UTCEchelonGraph re-scored
  69. 2026-10-19 01:52 UTCVendor advisory
  70. 2026-10-19 01:51 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-10-18 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  72. 2026-10-18 09:56 UTCEchelonGraph re-scored
  73. 2026-10-18 02:52 UTCEchelonGraph re-scored
  74. 2026-10-18 02:52 UTCVendor advisory
  75. 2026-10-18 02:52 UTCGHSA enrichmentGHSA-2q4x-j5p2-9wxv · GitHub severity HIGH · GitHub CVSS 7.8

Frequently asked(6)

What is CVE-2019-1214?
CVE-2019-1214 is a critical-severity vulnerability; its CVE record was published on September 11, 2019. An elevation of privilege vulnerability exists when the Windows Common Log File System (CLFS) driver improperly handles objects in memory, aka 'Windows Common Log File System Driver Elevation of Privilege Vulnerability'.
When was the CVE record for CVE-2019-1214 published?
The CVE record for CVE-2019-1214 was published on September 11, 2019. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 29, 2025; the record at its source may have been updated since.
Is CVE-2019-1214 actively exploited?
Yes. CISA added CVE-2019-1214 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 attention. A fix is available. Apply it.
What is the CVSS score of CVE-2019-1214?
CVE-2019-1214 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 (CRITICAL).
Which products are affected by CVE-2019-1214?
CVE-2019-1214 affects Microsoft Windows.
How do I remediate CVE-2019-1214?
A fix for CVE-2019-1214 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-1214 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2019-1214?

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