CVE-2019-1214

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: 1%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 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.0(high)
EPSS
69.6%
KEV
⚠ Exploited

Published

September 11, 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-1214
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-1214

Weakness Classification(1)

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

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 132× in last 7d / 569× 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 720 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2019-1214?
CVE-2019-1214 is a high vulnerability 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 CVE-2019-1214 disclosed?
CVE-2019-1214 was first published in the National Vulnerability Database on September 11, 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-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 patching attention.
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.
Which products are affected by CVE-2019-1214?
CVE-2019-1214 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-1214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-1214, 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-1214

Explore →

Is Your Infrastructure Affected by CVE-2019-1214?

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

Start Free Scan →Browse All CVEs