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

published 2020-06-09 6y ago modified 2026-06-17 4mo ago also EUVD-2020-12104

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

A remote code execution vulnerability exists in Microsoft Excel software when the software fails to properly handle objects in memory, aka 'Microsoft Excel Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1226.

Patch / fix

links 1

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

Is CVE-2020-1225 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

17.49% 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	8.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

Microsoft Microsoft 365 Apps for Enterprise for 32-bit Systems
Microsoft Microsoft 365 Apps for Enterprise for 64-bit Systems
Microsoft Microsoft Office
Microsoft Microsoft Excel

Classification

Weakness

CWE-416 Use After Free

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2020-1225
patch, vendor-advisory
talosintelligence.com /vulnerability_reports/TALOS-2020-1045
third-party-advisory

Sources

CVE List CVE-2020-1225
NVD CVE-2020-1225

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.