Microsoft Windows
Microsoft COM for Windows Deserialization of Untrusted Data Vulnerability
A remote code execution vulnerability exists in "Microsoft COM for Windows" when it fails to properly handle serialized objects, aka "Microsoft COM for Windows Remote Code Execution Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.
Timeline
Days relative to CVE publicationFirst public PoC 39 days after publication; added to CISA KEV 6.2 years after publication. First PoC: Microsoft COM for Windows - Privilege Escalation (Exploit-DB, 18 Jun 2018).
PoC repositories
Found on GitHub.1 informational
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| codewhitesec/UnmarshalPwn | 15 Jun 2018 +37 d | 88 | Informational · write-up |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| CVE record (tagged exploit) | 44906 | unknown | 14 Nov 2026 |
| Exploit-DB | Microsoft COM for Windows - Privilege Escalation | 18 Jun 2018 | 14 Nov 2026 |
| Metasploit | Metasploit post: Windows unmarshal post exploitation (post/windows/escalate/unmarshal_cmd_exec) | 19 Oct 2018 | 14 Nov 2026 |