CVE & CISA-KEV Catalog

CVE-2018-0802

HIGHCISA KEVEPSS 100th pctl
7.8
CVSS v3
NVD

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.

How to fix

Actively exploited, no published fix found yet

CISA required action: Apply updates per vendor instructions.

Federal remediation due: 2022-05-03

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploit Intelligence

87.42%probability of exploitation in 30 days
100thpercentile

Very high risk: more likely to be exploited than 100% of all known CVEs.

Known Exploited Vulnerability (CISA KEV)

Microsoft Office Memory Corruption Vulnerability

Microsoft Office contains a memory corruption vulnerability due to the way objects are handled in memory. Successful exploitation allows for remote code execution in the context of the current user. This vulnerability is known to be chained with CVE-2018-0798.

Apply updates per vendor instructions.

Remediation due: 2022-05-03

References

Related Vulnerabilities

Other CWE-787 (Out-of-bounds Write) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2025-22457Critical9.0100%KEV + RansomFix
CVE-2025-0282Critical9.0100%KEV + Ransom-
CVE-2015-3113Critical9.8100%KEVFix
CVE-2021-20038Critical9.8100%KEV + Ransom-
CVE-2023-4863High8.8100%KEVFix
CVE-2020-16040Medium6.5100%-Fix

Common questions

How do I fix CVE-2018-0802?

No published fix for CVE-2018-0802 has been found yet. It is on the CISA Known Exploited Vulnerabilities list; federal agencies must remediate by 2022-05-03. Apply the vendor's mitigations per CISA's guidance.

Is CVE-2018-0802 being actively exploited?

Yes. CVE-2018-0802 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. US federal agencies were required to remediate it by 2022-05-03. Treat it as a priority whatever its CVSS score says.

How severe is CVE-2018-0802?

CVE-2018-0802 has a CVSS v3 base score of 7.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2018-0802
CVE-2018-0802 severity badge

Markdown

[![CVE-2018-0802](https://tridentstack.com/cve/badge/CVE-2018-0802.svg)](https://tridentstack.com/cve/CVE-2018-0802)

HTML

<a href="https://tridentstack.com/cve/CVE-2018-0802"><img src="https://tridentstack.com/cve/badge/CVE-2018-0802.svg" alt="CVE-2018-0802"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-10-28.