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.
CVE-2017-0213
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.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 9.0(high)
- EPSS
- 99.7%
- KEV
- ⚠ Exploited
Published
May 12, 2017
Last Modified
April 22, 2026
Advisory Details (5)
Auto-updated May 20, 2026Known 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-0213Microsoft Windows - COM Aggregate Marshaler/IRemUnknown2 Type Confusion Privilege Escalation - Windows local Exploit
https://www.exploit-db.com/exploits/42020/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-0213All 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 136× in last 7d / 575× 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 756 total refreshes for this CVE.
- 2026-07-07 11:30 UTCEG score recompute
- 2026-07-07 11:30 UTCVendor advisory
- 2026-07-07 11:29 UTCGHSA enrichment
- 2026-07-07 07:42 UTCEG score recompute
- 2026-07-07 07:42 UTCVendor advisory
- 2026-07-07 07:42 UTCGHSA enrichment
- 2026-07-07 03:55 UTCEG score recompute
- 2026-07-07 03:55 UTCVendor advisory
- 2026-07-07 03:55 UTCGHSA enrichment
- 2026-07-07 00:08 UTCEG score recompute
- 2026-07-07 00:08 UTCVendor advisory
- 2026-07-07 00:08 UTCGHSA enrichment
- 2026-07-06 20:21 UTCEG score recompute
- 2026-07-06 20:21 UTCVendor advisory
- 2026-07-06 20:21 UTCGHSA enrichment
- 2026-07-06 16:32 UTCEG score recompute
- 2026-07-06 16:32 UTCVendor advisory
- 2026-07-06 16:32 UTCGHSA enrichment
- 2026-07-06 12:44 UTCEG score recompute
- 2026-07-06 12:44 UTCVendor advisory
- 2026-07-06 12:44 UTCGHSA enrichment
- 2026-07-06 08:57 UTCEG score recompute
- 2026-07-06 08:57 UTCVendor advisory
- 2026-07-06 08:57 UTCGHSA enrichment
- 2026-07-06 05:08 UTCEG score recompute
Show 75 moreShow fewer
- 2026-07-06 05:08 UTCVendor advisory
- 2026-07-06 05:08 UTCGHSA enrichment
- 2026-07-06 01:22 UTCEG score recompute
- 2026-07-06 01:22 UTCVendor advisory
- 2026-07-06 01:22 UTCGHSA enrichment
- 2026-07-05 21:36 UTCEG score recompute
- 2026-07-05 21:36 UTCVendor advisory
- 2026-07-05 21:36 UTCGHSA enrichment
- 2026-07-05 17:49 UTCEG score recompute
- 2026-07-05 17:49 UTCVendor advisory
- 2026-07-05 17:49 UTCGHSA enrichment
- 2026-07-05 14:02 UTCEG score recompute
- 2026-07-05 14:02 UTCVendor advisory
- 2026-07-05 14:02 UTCGHSA enrichment
- 2026-07-05 10:13 UTCEG score recompute
- 2026-07-05 10:13 UTCVendor advisory
- 2026-07-05 10:13 UTCGHSA enrichment
- 2026-07-05 06:27 UTCEG score recompute
- 2026-07-05 06:27 UTCVendor advisory
- 2026-07-05 06:26 UTCGHSA enrichment
- 2026-07-05 02:38 UTCEG score recompute
- 2026-07-05 02:38 UTCVendor advisory
- 2026-07-05 02:37 UTCGHSA enrichment
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-04 22:49 UTCEG score recompute
- 2026-07-04 22:49 UTCVendor advisory
- 2026-07-04 22:49 UTCGHSA enrichment
- 2026-07-04 19:03 UTCEG score recompute
- 2026-07-04 19:03 UTCVendor advisory
- 2026-07-04 19:03 UTCGHSA enrichment
- 2026-07-04 15:17 UTCEG score recompute
- 2026-07-04 15:17 UTCVendor advisory
- 2026-07-04 15:17 UTCGHSA enrichment
- 2026-07-04 11:31 UTCEG score recompute
- 2026-07-04 11:31 UTCVendor advisory
- 2026-07-04 11:30 UTCGHSA enrichment
- 2026-07-04 07:44 UTCEG score recompute
- 2026-07-04 07:44 UTCVendor advisory
- 2026-07-04 07:44 UTCGHSA enrichment
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-04 03:57 UTCEG score recompute
- 2026-07-04 03:57 UTCVendor advisory
- 2026-07-04 03:56 UTCGHSA enrichment
- 2026-07-04 00:08 UTCEG score recompute
- 2026-07-04 00:08 UTCVendor advisory
- 2026-07-04 00:08 UTCGHSA enrichment
- 2026-07-03 20:21 UTCEG score recompute
- 2026-07-03 20:21 UTCVendor advisory
- 2026-07-03 20:21 UTCGHSA enrichment
- 2026-07-03 16:35 UTCEG score recompute
- 2026-07-03 16:35 UTCVendor advisory
- 2026-07-03 16:35 UTCGHSA enrichment
- 2026-07-03 12:49 UTCEG score recompute
- 2026-07-03 12:49 UTCVendor advisory
- 2026-07-03 12:49 UTCGHSA enrichment
- 2026-07-03 09:03 UTCEG score recompute
- 2026-07-03 09:03 UTCVendor advisory
- 2026-07-03 09:03 UTCGHSA enrichment
- 2026-07-03 05:16 UTCEG score recompute
- 2026-07-03 05:16 UTCVendor advisory
- 2026-07-03 05:16 UTCGHSA enrichment
- 2026-07-03 01:28 UTCEG score recompute
- 2026-07-03 01:28 UTCVendor advisory
- 2026-07-03 01:28 UTCGHSA enrichment
- 2026-07-02 21:42 UTCEG score recompute
- 2026-07-02 21:42 UTCVendor advisory
- 2026-07-02 21:42 UTCGHSA enrichment
- 2026-07-02 17:56 UTCEG score recompute
- 2026-07-02 17:56 UTCVendor advisory
- 2026-07-02 17:55 UTCGHSA enrichment
- 2026-07-02 14:09 UTCEG score recompute
- 2026-07-02 14:09 UTCVendor advisory
- 2026-07-02 14:09 UTCGHSA enrichment
- 2026-07-02 10:23 UTCEG score recompute
- 2026-07-02 10:23 UTCVendor advisory
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.
- GitHub PoCeonrickity/CVE-2017-0213First 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-0213First seen Jul 1, 2017
CVE-2017-0213 for command line
Open source ↗ - Exploit-DBEDB-42020✓ verifiedFirst seen May 17, 2017
Microsoft Windows - COM Aggregate Marshaler/IRemUnknown2 Type Confusion Privilege Escalation
Open source ↗
Related CVEs(same vendor)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 93%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Frequently asked(6)
What is CVE-2017-0213?
When was CVE-2017-0213 disclosed?
Is CVE-2017-0213 actively exploited?
What is the CVSS score of CVE-2017-0213?
Which products are affected by CVE-2017-0213?
How do I remediate CVE-2017-0213?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-0213
Is Your Infrastructure Affected by CVE-2017-0213?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.