CVE-2020-16929

Microsoft Excel Remote Code Execution Vulnerability

HIGH
7.8
CVSS Score
Published: October 16, 2020 at 10:17 PM UTC
Updated: June 17, 2026 at 02:58 AM UTC
12 products affected across 1 vendorOffice365 AppsSharePoint Server

Using Microsoft SharePoint Enterprise Server 2013 Service Pack 1 by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft SharePoint Enterprise Server 2013 Service Pack 1 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 4%

Description

<p>A remote code execution vulnerability exists in Microsoft Excel software when the software fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.</p> <p>Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of Microsoft Excel. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) containing a specially crafted file designed to exploit the vulnerability. An attacker would have no way to force users to visit the website. Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an email or instant message, and then convince them to open the specially crafted file.</p> <p>The security update addresses the vulnerability by correcting how Microsoft Excel handles objects in memory.</p>

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

16.0.1 ≤ v < https://aka.ms/OfficeSecurityReleases16.0.1
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
13.0.0.0 ≤ v < publication15.0.0.0 ≤ v < publication16.0.0.0 ≤ v < publication13.0.0.015.0.0.016.0.0.020102010 sp220132013 sp12016
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
13.0.0.0 ≤ v < publication13.0.0.020102010 sp2
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
16.0.1 ≤ v < publication1.016.0.1
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
13.0.0 ≤ v < publication15.0.0.0 ≤ v < publication13.0.015.0.0.020102010 sp220132013 sp1
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
15.0.0 ≤ v < publication15.0.02013 sp1
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
13.0.0.0 ≤ v < publication13.0.0.020102010 sp22013
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
13.0.0.0 ≤ v < publication13.0.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
15.0.0 ≤ v < publication15.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card