Skip to content
Exploit Radar Choose my productsProducts My radar
English

Patch first › Microsoft

Exploited CVE from 2018, added in 2024

CVE-2018-0824

Microsoft Windows · Operating systems

Microsoft COM for Windows Deserialization of Untrusted Data Vulnerability

What should I do? View at Microsoft

At a glance

Exploited. Added to CISA’s catalog of exploited vulnerabilities on August 5, 2024.

Affected product: Microsoft Windows (category Operating systems, indicative classification). Name in CISA’s catalog: Microsoft Windows.

What should I do?

Apply the patches or mitigations from Microsoft; if none are available, stop using the product.

Deadline set by CISA for US federal agencies: 21 days (due August 26, 2024). It only binds those agencies, but it is a useful measure of urgency.

Original text of the required action (CISA)

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Timeline

  1. Vulnerability published Publication date (NVD)
  2. Exploitation confirmed Added to CISA’s KEV catalog
  3. CISA deadline Remediation deadline set for US federal agencies

The facts, with their sources

Exploitation confirmed
Yes, on August 5, 2024 Date added to the catalog of exploited vulnerabilities. Exploitation itself may have started earlier. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
Ransomware
No known use to date That does not guarantee it is not being used: the information is not public. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
Hunt for compromise
Not requested by CISA Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
CISA required action
Apply the patches or mitigations from Microsoft; if none are available, stop using the product. Rewritten by this site from CISA’s original text. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
CISA deadline
August 26, 2024, 21 days Set for US federal agencies: a measure of urgency, not an obligation elsewhere. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
Microsoft patch
Not available Source: Security Update Guide, collected September 29, 2026 at 14:57 UTC
Vulnerability published
May 9, 2018 Source: National Vulnerability Database (NVD), collected September 29, 2026 at 15:00 UTC
Product according to CISA
Microsoft Windows Filed by this site under “Operating systems” (indicative classification). Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Technical detail of the score: attack vector, complexity, impact. Source: National Vulnerability Database (NVD), collected September 29, 2026 at 15:00 UTC

Severity and activity

8.8 / 10 CVSS severity: high

Score from the NVD. Collected Sep 29, 2026.

— Probability of exploitation in the next 30 days (EPSS)

FIRST’s EPSS model. Since exploitation is already confirmed, this figure is mostly useful to compare activity. Collected Sep 29, 2026.

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.

Official description from the NVD, collected Sep 29, 2026. CVE® description © The MITRE Corporation.

Microsoft COM for Windows contains a deserialization of untrusted data vulnerability that allows for privilege escalation and remote code execution via a specially crafted file or script.

Summary from CISA (KEV catalog).

CERT-FR advisories

No advisory among the latest CERT-FR publications this site follows. That does not mean there are none.

Information reused under the Open Licence 2.0 (Etalab); the date of last update is shown for each advisory. This site is neither affiliated with nor endorsed by ANSSI.

Sources for this page