# CVE-2018-0824: Microsoft COM for Windows Deserialization of Untrusted Data

> Remote attackers can execute arbitrary code by exploiting improper handling of serialized objects in Microsoft COM for Windows.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 5 Aug 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 May 2018
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-6w8g-777w-9mcc

## What is CVE-2018-0824?

CVE-2018-0824 is a high-severity unsafe deserialization vulnerability in Microsoft Windows 10 1507, published on 9 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2018-0824?

It affects 13 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1703, Microsoft Windows 10 1709, Microsoft Windows 10 1803, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 1709, Microsoft Windows Server 1803, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016.

## How do I fix CVE-2018-0824?

No fix has been published for CVE-2018-0824 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 26 Aug 2024.

## Is CVE-2018-0824 being exploited?

Yes. Attackers have exploited CVE-2018-0824 in the wild since at least 5 Aug 2024.

Public exploit code:

- POC for CVE-2018-0824 (github_poc): https://github.com/codewhitesec/UnmarshalPwn
- Microsoft COM for Windows - Privilege Escalation (exploitdb)
- Windows unmarshal post exploitation (metasploit)

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0824 and fix it if it is affected.

What it is: CVE-2018-0824 is a high-severity unsafe deserialization vulnerability in Microsoft Windows 10 1507, published on 9 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2018-0824 in the wild since at least 5 Aug 2024.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-0824/ (Markdown: https://insights.sbomify.com/CVE-2018-0824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-0824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-0824
- OSV: https://osv.dev/vulnerability/CVE-2018-0824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-0824/
Summaries are generated and may contain mistakes; the official description above is the record.