Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2018-0798: Microsoft Office Equation Editor Memory Corruption RCE

Published Jan 10, 2018 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS95.1%100th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2018-0798CWE-119

CVE-2018-0798 is a memory corruption vulnerability in Microsoft Equation Editor affecting Microsoft Office 2007, 2010, 2013, and 2016. Improper handling of objects in memory, associated with Equation Editor MATRIX processing, allows a specially crafted document to execute arbitrary code when opened in an affected Microsoft Office application or Microsoft WordPad. Exploitation executes code in the context of the current user. The vulnerability has been exploited through weaponized RTF documents, including documents generated by Royal Road.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary code execution with the current user's privileges. An attacker can install malware and access, modify, or delete data accessible to that user. If the user has administrative privileges, exploitation can result in full system compromise, including installation of programs and creation of accounts with full user rights. Observed exploitation has enabled delivery of remote access trojans and establishment of an initial foothold for espionage operations.

Mitigation

If you can’t patch tonight, do this now.

Avoid opening untrusted documents, particularly unexpected email attachments or files obtained through unsolicited links. Filter or quarantine suspicious Office and RTF documents before delivery to users. Run Office applications under accounts without administrative privileges to limit the consequences of successful exploitation.

Remediation

Patch, then assume compromise.

Apply Microsoft's security update released on January 9, 2018, for the affected Office installation. The update addresses the vulnerability by removing legacy Equation Editor functionality, as documented in Microsoft support article 4057882.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationMicrosoft Officeapplication
Microsoft CorporationOffice Compatibility Packapplication
Microsoft CorporationWordapplication
FAQ

Frequently asked questions

Is CVE-2018-0798 exploited in the wild?
Yes. As of Nov 5, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2018-0798?
As of Nov 5, 2026, Mallory has found no public exploit for CVE-2018-0798.
Is there a patch for CVE-2018-0798?
Apply Microsoft's security update released on January 9, 2018, for the affected Office installation. The update addresses the vulnerability by removing legacy Equation Editor functionality, as documented in Microsoft support article 4057882.
What products are affected by CVE-2018-0798?
Microsoft Corporation Microsoft Office, Microsoft Corporation Word, and Microsoft Corporation Office Compatibility Pack.
How severe is CVE-2018-0798?
CVE-2018-0798 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 95.1% (100th percentile) as of Nov 5, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence36Every report linking this CVE to a named adversary.
Associated malware37Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.