CVE-2017-0213

CRITICALNVD 7.39.0▲
EchelonGraph scoreHIGH confidence

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

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 84%CVSS: 7.3Exploit: cisa kev · ssvc active · kev ransomware · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

Windows COM Aggregate Marshaler in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows an elevation privilege vulnerability when an attacker runs a specially crafted application, aka "Windows COM Elevation of Privilege Vulnerability". This CVE ID is unique from CVE-2017-0214.

CVSS v3
7.3
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
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
84%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 12, 2017

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated May 20, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa, microsoft.
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-2017-0213
generic🟡 PoC Available

Microsoft Windows - COM Aggregate Marshaler/IRemUnknown2 Type Confusion Privilege Escalation - Windows local Exploit

https://www.exploit-db.com/exploits/42020/
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-2017-0213
generic
http://www.securitytracker.com/id/1038457
generic
http://www.securityfocus.com/bid/98102

Vendor Advisories for CVE-2017-0213(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 92× in last 7d / 400× 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 1,664 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

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

  • Exploit-DBEDB-42020✓ verified
    First seen May 17, 2017

    Microsoft Windows - COM Aggregate Marshaler/IRemUnknown2 Type Confusion Privilege Escalation

    Open source ↗
  • GitHub PoCeonrickity/CVE-2017-0213
    First seen Apr 10, 2018

    Fixed No Virus Manual Automatic Loader exe no zip because zip picks up the anti virus detector.

    Open source ↗
  • GitHub PoCzcgonvh/CVE-2017-0213
    First seen Jul 1, 2017

    CVE-2017-0213 for command line

    Open source ↗

Frequently asked(6)

What is CVE-2017-0213?
CVE-2017-0213 is a critical vulnerability published on May 12, 2017. Windows COM Aggregate Marshaler in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows an elevation privilege vulnerability when an attacker runs a specially…
When was CVE-2017-0213 disclosed?
CVE-2017-0213 was first published on May 12, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-0213 actively exploited?
Yes. CISA added CVE-2017-0213 to the Known Exploited Vulnerabilities catalog on March 28, 2022, 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-2017-0213?
CVE-2017-0213 has a CVSS v3 base score of 7.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2017-0213?
CVE-2017-0213 affects Microsoft Windows.
How do I remediate CVE-2017-0213?
A fix for CVE-2017-0213 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-0213 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-0213

Explore →

Is Your Infrastructure Affected by CVE-2017-0213?

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

Book a Demo →Browse All CVEs