CVE-2018-0802

CRITICALNVD 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
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 93%CVSS: 7.8Exploit: cisa kev · ssvc active · kev ransomware · epss top5pct · epss high · public exploitExposed: 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 PROB
93%
EPSS %ILE
100%
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 96× in last 7d / 397× 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 1,291 total refreshes for this CVE.

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

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 critical 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.