CVE Intelligence
CISA KEV High Insecure deserialization exploit reference

CVE-2018-0824 — 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.

Published May 9, 2018 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (exploitdb)+8
  • EPSS 73.2% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Aug 5, 2024
EPSS FIRST
73.19%
ahead of 99% of scored CVEs · Oct 14, 2026
Affects
Microsoft
Windows 10 1507 and 12 more
CVSS base
8.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

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

US federal deadline: Aug 26, 2024 — passed 780 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1703…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  6. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
  7. Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Windows 10 1507 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1607 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1703 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1709 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1803 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 7 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 8.1 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Rt 8.1 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 1709 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 1803 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2008 versions not specified by the sourceversion r2-sp1 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2012 versions not specified by the sourceversion r2 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2016 versions not specified by the source Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.5 CVSS 3.1 High 1.6 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
7.5 CVSS 3.0 High — — GitHub, Inc. via GitHub Security Advisories
5.1 CVSS 2.0 Medium 4.9 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-502 · Deserialization of Untrusted Data

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Aug 5, 2024
Federal deadline
Aug 26, 2024
passed 780 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 73.19%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor serialized objects in requests and unexpected processes spawned by the runtime.
  • Hunt retroactively in logs from before Aug 5, 2024 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/windows 10 1507, microsoft/windows 10 1607, microsoft/windows 10 1703, microsoft/windows 10 1709, microsoft/wi
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5 → 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.5
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2024
  • Added to CISA KEV catalog
    Aug 4, 2024 · CISA
  • 2018
  • CVE published
    May 9, 2018 · microsoft

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

8 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
2024-08
what else CISA listed that month
CWE-502
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97841 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2018-0824 is "Microsoft COM for Windows Deserialization of Untrusted Data Vulnerability", rated High. It affects Windows 10 1507 (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 73.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.