How severe is CVE-2018-0802?

CVE-2018-0802 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-0802?

Affected package information for CVE-2018-0802 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2018-0802?

No fixed version has been published for CVE-2018-0802 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2018-0802 actively exploited in the wild?

Yes. There are 20 known exploit references for CVE-2018-0802, including 15 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-0802?

CVE-2018-0802 has an EPSS (Exploit Prediction Scoring System) score of 94.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2018-0802 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2018-0802 (Microsoft Office Memory Corruption Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2018-0802?

CVE-2018-0802 is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2018-0802?

CVE-2018-0802 affects microsoft office (4 versions, e.g. 2007, 2010, 2013…); microsoft office compatibility pack; microsoft word (4 versions, e.g. 2007, 2010, 2013…). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2018-0802 published, and has it been updated?

CVE-2018-0802 was published on January 10, 2018 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

CVE-2018-0802

HIGH

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…

Published

Jan 10, 2018

Updated

Oct 28, 2025

Affected

0 pkgs

Patched

None yet

Exploits

20 known

EPSS Exploitation Probability

via FIRST.org ↗

94.1%probability of exploitation in next 30 days

Very High Risk100th percentile+0.18%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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.

Affected Products

3 products · 11 configurations

Application

officemicrosoft

4 versions

2007201020132016

Application

office compatibility packmicrosoft

all

Application

wordmicrosoft

4 versions

2007201020132016

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.