Equation Editor in Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allows a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Office Memory Corruption Vulnerability".
CVE-2018-0798
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 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.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 computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 99.9%
- KEV
- ⚠ Exploited
Published
January 10, 2018
Last Modified
October 28, 2025
Advisory Details (4)
Auto-updated Jun 2, 2026Known 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-0798Security 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-0798Weakness 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 66× in last 7d / 333× 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 601 total refreshes for this CVE.
- 2026-07-23 01:31 UTCEG score recompute
- 2026-07-22 22:47 UTCVendor advisory
- 2026-07-22 22:47 UTCGHSA enrichment
- 2026-07-22 22:11 UTCEG score recompute
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 18:21 UTCGHSA enrichment
- 2026-07-22 13:57 UTCGHSA enrichment
- 2026-07-22 09:33 UTCVendor advisory
- 2026-07-22 09:33 UTCGHSA enrichment
- 2026-07-22 05:10 UTCVendor advisory
- 2026-07-22 05:10 UTCGHSA enrichment
- 2026-07-22 00:45 UTCVendor advisory
- 2026-07-22 00:45 UTCGHSA enrichment
- 2026-07-21 18:12 UTCVendor advisory
- 2026-07-21 18:12 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 13:48 UTCVendor advisory
- 2026-07-21 13:48 UTCGHSA enrichment
- 2026-07-21 09:25 UTCVendor advisory
- 2026-07-21 09:25 UTCGHSA enrichment
- 2026-07-21 05:01 UTCVendor advisory
- 2026-07-21 05:01 UTCGHSA enrichment
- 2026-07-21 00:36 UTCVendor advisory
- 2026-07-21 00:36 UTCGHSA enrichment
- 2026-07-20 20:12 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-20 20:12 UTCGHSA enrichment
- 2026-07-20 15:49 UTCGHSA enrichment
- 2026-07-20 11:25 UTCGHSA enrichment
- 2026-07-20 07:01 UTCVendor advisory
- 2026-07-20 07:01 UTCGHSA enrichment
- 2026-07-20 02:38 UTCVendor advisory
- 2026-07-20 02:38 UTCGHSA enrichment
- 2026-07-19 22:14 UTCVendor advisory
- 2026-07-19 22:14 UTCGHSA enrichment
- 2026-07-19 17:50 UTCVendor advisory
- 2026-07-19 17:50 UTCGHSA enrichment
- 2026-07-19 13:27 UTCVendor advisory
- 2026-07-19 13:26 UTCGHSA enrichment
- 2026-07-19 09:03 UTCVendor advisory
- 2026-07-19 09:03 UTCGHSA enrichment
- 2026-07-19 04:39 UTCVendor advisory
- 2026-07-19 04:39 UTCGHSA enrichment
- 2026-07-19 00:15 UTCGHSA enrichment
- 2026-07-18 19:51 UTCVendor advisory
- 2026-07-18 19:51 UTCGHSA enrichment
- 2026-07-18 15:27 UTCVendor advisory
- 2026-07-18 15:27 UTCGHSA enrichment
- 2026-07-18 11:03 UTCVendor advisory
- 2026-07-18 11:03 UTCGHSA enrichment
- 2026-07-18 06:39 UTCVendor advisory
- 2026-07-18 06:39 UTCGHSA enrichment
- 2026-07-18 02:16 UTCVendor advisory
- 2026-07-18 02:16 UTCGHSA enrichment
- 2026-07-17 21:52 UTCVendor advisory
- 2026-07-17 21:52 UTCGHSA enrichment
- 2026-07-17 17:28 UTCVendor advisory
- 2026-07-17 17:27 UTCGHSA enrichment
- 2026-07-17 13:04 UTCVendor advisory
- 2026-07-17 13:03 UTCGHSA enrichment
- 2026-07-17 08:39 UTCEG score recompute
- 2026-07-17 08:39 UTCVendor advisory
- 2026-07-17 08:39 UTCGHSA enrichment
- 2026-07-17 04:15 UTCVendor advisory
- 2026-07-17 04:15 UTCGHSA enrichment
- 2026-07-16 23:52 UTCVendor advisory
- 2026-07-16 23:52 UTCGHSA enrichment
- 2026-07-16 19:29 UTCVendor advisory
- 2026-07-16 19:29 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 15:04 UTCGHSA enrichment
- 2026-07-16 10:41 UTCVendor advisory
- 2026-07-16 10:40 UTCGHSA enrichment
- 2026-07-16 06:14 UTCVendor advisory
- 2026-07-16 06:14 UTCGHSA enrichment
- 2026-07-16 01:50 UTCVendor advisory
- 2026-07-16 01:50 UTCGHSA enrichment
- 2026-07-15 21:26 UTCVendor advisory
- 2026-07-15 21:26 UTCGHSA enrichment
- 2026-07-15 17:03 UTCVendor advisory
- 2026-07-15 17:03 UTCGHSA enrichment
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 12:36 UTCVendor advisory
- 2026-07-15 12:36 UTCGHSA enrichment
- 2026-07-15 08:12 UTCVendor advisory
- 2026-07-15 08:12 UTCGHSA enrichment
- 2026-07-15 03:48 UTCVendor advisory
- 2026-07-15 03:48 UTCGHSA enrichment
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-14 23:25 UTCVendor advisory
- 2026-07-14 23:25 UTCGHSA enrichment
- 2026-07-14 19:00 UTCVendor advisory
- 2026-07-14 18:59 UTCGHSA enrichment
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 14:33 UTCVendor advisory
- 2026-07-14 14:33 UTCGHSA enrichment
- 2026-07-14 10:10 UTCVendor advisory
- 2026-07-14 10:10 UTCGHSA enrichment
- 2026-07-14 05:46 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-787
- CVE-2007-0158EG 9.8CRITICAL
- CVE-2007-0899EG 9.8CRITICAL
- CVE-2011-2462EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2010-20115EG 9.3CRITICAL
- CVE-2010-4398NVD 7.8EG 9.0 KEVEPSS 95%HIGH
- CVE-2010-3333NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-2883NVD 7.3EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-1297NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-3953NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-3129NVD 7.8EG 9.0 KEVEPSS 100%HIGH
Frequently asked(6)
What is CVE-2018-0798?
When was CVE-2018-0798 disclosed?
Is CVE-2018-0798 actively exploited?
What is the CVSS score of CVE-2018-0798?
Which products are affected by CVE-2018-0798?
How do I remediate CVE-2018-0798?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2018-0798
Is Your Infrastructure Affected by CVE-2018-0798?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.