# CVE-2018-0798: Microsoft Office Memory Corruption

> Remote attackers can execute arbitrary code via memory corruption in the Microsoft Office Equation Editor component.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jan 2018
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-4prc-qxrc-76p6

## What is CVE-2018-0798?

CVE-2018-0798 is a high-severity memory corruption vulnerability in Microsoft Office, published on 10 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-0798?

It affects 3 products.


Products: Microsoft Office, Microsoft Office Compatibility Pack, Microsoft Word.

## How do I fix CVE-2018-0798?

No fix has been published for CVE-2018-0798 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2018-0798 being exploited?

Yes. Attackers have exploited CVE-2018-0798 in the wild since at least 3 Nov 2021.

Public exploit code:

- CVE-2018-0798复现 (github_poc): https://github.com/Sunqiz/CVE-2018-0798-reproduction

## Other vulnerabilities in Microsoft Office

- [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild)
- [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild)
- [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-8570](https://insights.sbomify.com/CVE-2017-8570/): Microsoft Office Remote Code Execution (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0798 and fix it if it is affected.

What it is: CVE-2018-0798 is a high-severity memory corruption vulnerability in Microsoft Office, published on 10 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2018-0798 in the wild since at least 3 Nov 2021.

Affected product: Microsoft Office. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-0798/ (Markdown: https://insights.sbomify.com/CVE-2018-0798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-0798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-0798
- OSV: https://osv.dev/vulnerability/CVE-2018-0798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-0798/
Summaries are generated and may contain mistakes; the official description above is the record.