CVE-2018-0824

HIGHNVD 8.89.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-08-05), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
8.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 73%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
EPSS
99.4%
KEV
⚠ Exploited

Published

May 9, 2018

Last Modified

October 28, 2025

Advisory Details (4)

Auto-updated Jun 2, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft, cisa.
cisa Patch Available🔴 Active Exploitation

Known 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-2018-0824
microsoft Patch Available

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-2018-0824

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All 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 99× in last 7d / 412× 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 711 total refreshes for this CVE.

  1. 2026-07-22 22:11 UTCEG score recompute
  2. 2026-07-22 20:13 UTCGHSA enrichment
  3. 2026-07-22 19:40 UTCCISA KEV update
  4. 2026-07-22 16:22 UTCEG score recompute
  5. 2026-07-22 16:22 UTCVendor advisory
  6. 2026-07-22 16:22 UTCGHSA enrichment
  7. 2026-07-22 14:04 UTCEPSS rescore
  8. 2026-07-22 12:25 UTCVendor advisory
  9. 2026-07-22 12:25 UTCGHSA enrichment
  10. 2026-07-22 08:36 UTCVendor advisory
  11. 2026-07-22 08:36 UTCGHSA enrichment
  12. 2026-07-22 04:48 UTCVendor advisory
  13. 2026-07-22 04:47 UTCGHSA enrichment
  14. 2026-07-22 00:49 UTCVendor advisory
  15. 2026-07-22 00:49 UTCGHSA enrichment
  16. 2026-07-21 21:00 UTCVendor advisory
  17. 2026-07-21 20:59 UTCGHSA enrichment
  18. 2026-07-21 17:11 UTCVendor advisory
  19. 2026-07-21 17:11 UTCGHSA enrichment
  20. 2026-07-21 14:37 UTCCISA KEV update
  21. 2026-07-21 13:22 UTCVendor advisory
  22. 2026-07-21 13:22 UTCGHSA enrichment
  23. 2026-07-21 09:32 UTCVendor advisory
  24. 2026-07-21 09:32 UTCGHSA enrichment
  25. 2026-07-21 05:43 UTCVendor advisory
Show 75 more
  1. 2026-07-21 05:43 UTCGHSA enrichment
  2. 2026-07-21 01:53 UTCVendor advisory
  3. 2026-07-21 01:53 UTCGHSA enrichment
  4. 2026-07-20 22:04 UTCVendor advisory
  5. 2026-07-20 22:04 UTCGHSA enrichment
  6. 2026-07-20 18:16 UTCEG score recompute
  7. 2026-07-20 18:16 UTCVendor advisory
  8. 2026-07-20 18:16 UTCGHSA enrichment
  9. 2026-07-20 17:04 UTCEPSS rescore
  10. 2026-07-20 17:04 UTCEPSS rescore
  11. 2026-07-20 14:27 UTCGHSA enrichment
  12. 2026-07-20 10:39 UTCGHSA enrichment
  13. 2026-07-20 06:50 UTCVendor advisory
  14. 2026-07-20 06:50 UTCGHSA enrichment
  15. 2026-07-20 02:38 UTCVendor advisory
  16. 2026-07-20 02:38 UTCGHSA enrichment
  17. 2026-07-19 22:49 UTCVendor advisory
  18. 2026-07-19 22:49 UTCGHSA enrichment
  19. 2026-07-19 19:01 UTCVendor advisory
  20. 2026-07-19 19:01 UTCGHSA enrichment
  21. 2026-07-19 15:13 UTCVendor advisory
  22. 2026-07-19 15:13 UTCGHSA enrichment
  23. 2026-07-19 11:25 UTCVendor advisory
  24. 2026-07-19 11:25 UTCGHSA enrichment
  25. 2026-07-19 07:37 UTCVendor advisory
  26. 2026-07-19 07:37 UTCGHSA enrichment
  27. 2026-07-19 03:48 UTCEG score recompute
  28. 2026-07-19 03:48 UTCVendor advisory
  29. 2026-07-19 03:48 UTCGHSA enrichment
  30. 2026-07-19 02:26 UTCEPSS rescore
  31. 2026-07-19 02:26 UTCEPSS rescore
  32. 2026-07-18 23:59 UTCGHSA enrichment
  33. 2026-07-18 20:11 UTCVendor advisory
  34. 2026-07-18 20:11 UTCGHSA enrichment
  35. 2026-07-18 16:22 UTCVendor advisory
  36. 2026-07-18 16:22 UTCGHSA enrichment
  37. 2026-07-18 12:34 UTCEG score recompute
  38. 2026-07-18 12:34 UTCVendor advisory
  39. 2026-07-18 12:34 UTCGHSA enrichment
  40. 2026-07-18 10:01 UTCEPSS rescore
  41. 2026-07-18 08:46 UTCVendor advisory
  42. 2026-07-18 08:46 UTCGHSA enrichment
  43. 2026-07-18 04:58 UTCVendor advisory
  44. 2026-07-18 04:58 UTCGHSA enrichment
  45. 2026-07-18 01:10 UTCVendor advisory
  46. 2026-07-18 01:10 UTCGHSA enrichment
  47. 2026-07-17 21:22 UTCVendor advisory
  48. 2026-07-17 21:22 UTCGHSA enrichment
  49. 2026-07-17 17:33 UTCVendor advisory
  50. 2026-07-17 17:33 UTCGHSA enrichment
  51. 2026-07-17 13:45 UTCVendor advisory
  52. 2026-07-17 13:45 UTCGHSA enrichment
  53. 2026-07-17 09:57 UTCEG score recompute
  54. 2026-07-17 09:57 UTCVendor advisory
  55. 2026-07-17 09:57 UTCGHSA enrichment
  56. 2026-07-17 06:08 UTCVendor advisory
  57. 2026-07-17 06:08 UTCGHSA enrichment
  58. 2026-07-17 02:20 UTCVendor advisory
  59. 2026-07-17 02:19 UTCGHSA enrichment
  60. 2026-07-16 22:30 UTCVendor advisory
  61. 2026-07-16 22:30 UTCGHSA enrichment
  62. 2026-07-16 18:40 UTCVendor advisory
  63. 2026-07-16 18:40 UTCGHSA enrichment
  64. 2026-07-16 17:04 UTCCISA KEV update
  65. 2026-07-16 16:59 UTCEPSS rescore
  66. 2026-07-16 16:59 UTCEPSS rescore
  67. 2026-07-16 14:51 UTCVendor advisory
  68. 2026-07-16 14:50 UTCGHSA enrichment
  69. 2026-07-16 11:02 UTCVendor advisory
  70. 2026-07-16 11:02 UTCGHSA enrichment
  71. 2026-07-16 07:13 UTCVendor advisory
  72. 2026-07-16 07:13 UTCGHSA enrichment
  73. 2026-07-16 03:25 UTCVendor advisory
  74. 2026-07-16 03:25 UTCGHSA enrichment
  75. 2026-07-15 23:37 UTCVendor advisory

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitpost/windows/escalate/unmarshal_cmd_exec✓ verified
    First seen Aug 5, 2018

    Windows unmarshal post exploitation

    Open source ↗
  • Exploit-DBEDB-44906
    First seen Jun 18, 2018

    Microsoft COM for Windows - Privilege Escalation

    Open source ↗
  • GitHub PoCcodewhitesec/UnmarshalPwn
    First seen Jun 15, 2018

    POC for CVE-2018-0824

    Open source ↗

Frequently asked(6)

What is CVE-2018-0824?
CVE-2018-0824 is a high vulnerability published on May 9, 2018. 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…
When was CVE-2018-0824 disclosed?
CVE-2018-0824 was first published in the National Vulnerability Database on May 9, 2018, with the most recent update on October 28, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-0824 actively exploited?
Yes. CISA added CVE-2018-0824 to the Known Exploited Vulnerabilities catalog on August 5, 2024, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2018-0824?
CVE-2018-0824 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2018-0824?
CVE-2018-0824 affects Microsoft Windows. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2018-0824?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-0824, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-0824

Explore →

Is Your Infrastructure Affected by CVE-2018-0824?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.