CVE-2018-0802

HIGHNVD 7.89.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.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
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 93%CVSS: 7.8Exploit: NoneExposed: 0

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

Equation Editor in Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allow a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE is unique from CVE-2018-0797 and CVE-2018-0812.

CVSS v3
7.8
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
99.8%
KEV
⚠ Exploited

Published

January 10, 2018

Last Modified

October 28, 2025

Advisory Details (6)

Auto-updated Jun 4, 2026
🔬 Proof of concept available. Patch available. Sources: microsoft.
generic

Many Formulas, One Calc - Exploiting a New Office Equation Vulnerability - Check Point Research

https://research.checkpoint.com/another-office-equation-rce-vulnerability/
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-0802
generic

GitHub - zldww2011/CVE-2018-0802_POC: Exploit the vulnerability to execute the calculator · GitHub

https://github.com/zldww2011/CVE-2018-0802_POC
generic🟡 PoC Available

GitHub - rxwx/CVE-2018-0802: PoC Exploit for CVE-2018-0802 (and optionally CVE-2017-11882) · GitHub

https://github.com/rxwx/CVE-2018-0802

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 91× in last 7d / 398× 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 705 total refreshes for this CVE.

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

Publicly available exploits

(4 references)

Working exploit code is in the public domain (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoClikekabin/CVE-2018-0802_CVE-2017-11882
    First seen Jan 16, 2018
    Open source ↗
  • GitHub PoCRidter/RTF_11882_0802
    First seen Jan 12, 2018

    PoC for CVE-2018-0802 And CVE-2017-11882

    Open source ↗
  • GitHub PoCrxwx/CVE-2018-0802
    First seen Jan 11, 2018

    PoC Exploit for CVE-2018-0802 (and optionally CVE-2017-11882)

    Open source ↗
  • GitHub PoCzldww2011/CVE-2018-0802_POC
    First seen Jan 11, 2018

    Exploit the vulnerability to execute the calculator

    Open source ↗

Frequently asked(6)

What is CVE-2018-0802?
CVE-2018-0802 is a high vulnerability published on January 10, 2018. Equation Editor in Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allow a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE is unique from CVE-2018-0797…
When was CVE-2018-0802 disclosed?
CVE-2018-0802 was first published in the National Vulnerability Database on January 10, 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-0802 actively exploited?
Yes. CISA added CVE-2018-0802 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Office. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2018-0802?
CVE-2018-0802 has a CVSS v3 base score of 7.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-0802?
CVE-2018-0802 affects Microsoft Office. 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-0802?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-0802, 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-0802

Explore →

Is Your Infrastructure Affected by CVE-2018-0802?

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