A remote code execution vulnerability exists in Microsoft Office software when the software fails to properly handle objects in memory, aka…

published 2020-01-14 6y ago modified 2026-06-17 4mo ago also EUVD-2020-2145

cvss: 7.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 18.2%; EPSS 18.2% chance of exploitation in 30 days, percentile 97%
public exploits: 0; none known

A remote code execution vulnerability exists in Microsoft Office software when the software fails to properly handle objects in memory, aka 'Microsoft Office Memory Corruption Vulnerability'.

Patch / fix

links 1

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0652 advisory

Is CVE-2020-0652 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

18.21% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

Microsoft Microsoft Office
Microsoft Office 365 ProPlus

Classification

Weakness

CWE-787 Out-of-bounds Write

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2020-0652
patch, vendor-advisory
zerodayinitiative.com /advisories/ZDI-20-127/
third-party-advisory, vdb-entry

Sources

CVE List CVE-2020-0652
NVD CVE-2020-0652

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.