Skip to content
Server Security Center
KEVhigh7.8

CVE-2021-42292: Microsoft Excel Security Feature Bypass

Microsoft Office · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-17.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
43%
higher than 98.7% of all CVEs
Added to CISA KEV
2021-11-17
US federal due date 2021-12-01
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-42292 explained

CVE-2021-42292 is a security feature bypass vulnerability in Microsoft Excel, part of Microsoft Office, that would allow a local user to perform arbitrary code execution. CISA lists it as a known exploited vulnerability, so attackers are known to use it, and affected Office installations should be updated promptly.

Impact

A successful attack can lead to arbitrary code execution with high impact on confidentiality, integrity and availability. The attack vector is local, complexity is low, no privileges are required, but user interaction is required. CISA rates the technical impact as total, meaning total control of the affected component. CISA's SSVC marks it as not automatable. Attackers are known to exploit this vulnerability; ransomware use is unknown.

Who is affected

Microsoft Excel 2013 Service Pack 1 and Microsoft Office 2013 Service Pack 1 before 15.0.5397.1001 are fixed in 15.0.5397.1001. Microsoft Excel 2016 and Microsoft Office 2016 before 16.0.5239.1001 are fixed in 16.0.5239.1001. Microsoft Office 2019 for Mac and Microsoft Office LTSC for Mac 2021 before 16.55.21111400 are fixed in 16.55.21111400. For Microsoft 365 Apps for Enterprise, Microsoft Office 2019 and Microsoft Office LTSC 2021, builds before the fixed release are affected; the CVE record names no fixed version.

Written with AI from the data on this page and checked against it automatically.

Official description

A security feature bypass vulnerability in Microsoft Excel would allow a local user to perform arbitrary code execution.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft 365 Apps for Enterprise32-bit, x64
    Affected
    • builds before the fixed release (see vendor release notes)
    Fixed in
  • Microsoft Excel 2013 Service Pack 132-bit, ARM64, x64
    Affected
    • < 15.0.5397.1001
    Fixed in
    • 15.0.5397.1001
  • Microsoft Excel 201632-bit, x64
    Affected
    • < 16.0.5239.1001
    Fixed in
    • 16.0.5239.1001
  • Microsoft Office 2013 Service Pack 132-bit, ARM64, x64
    Affected
    • < 15.0.5397.1001
    Fixed in
    • 15.0.5397.1001
  • Microsoft Office 201632-bit, x64
    Affected
    • < 16.0.5239.1001
    Fixed in
    • 16.0.5239.1001
  • Microsoft Office 201932-bit, x64
    Affected
    • builds before the fixed release (see vendor release notes)
    Fixed in
  • Microsoft Office 2019 for Mac
    Affected
    • < 16.55.21111400
    Fixed in
    • 16.55.21111400
  • Microsoft Office LTSC 202132-bit, x64
    Affected
    • builds before the fixed release (see vendor release notes)
    Fixed in
  • Microsoft Office LTSC for Mac 2021
    Affected
    • < 16.55.21111400
    Fixed in
    • 16.55.21111400

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Excel 2013 Service Pack 1: 15.0.5397.1001
    • Microsoft Excel 2016: 16.0.5239.1001
    • Microsoft Office 2013 Service Pack 1: 15.0.5397.1001
    • Microsoft Office 2016: 16.0.5239.1001
    • Microsoft Office 2019 for Mac: 16.55.21111400
    • Microsoft Office LTSC for Mac 2021: 16.55.21111400
    For the other affected products the CVE record names no fixed version – see the table and the vendor advisory.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2021-42292
  • CISA's deadline for US federal agencies: 2021-12-01 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Update Excel 2013 SP1 and Office 2013 SP1 to 15.0.5397.1001 or later.
  2. Update Excel 2016 and Office 2016 to 16.0.5239.1001 or later.
  3. Update Office 2019 for Mac and Office LTSC for Mac 2021 to 16.55.21111400 or later.
  4. For Microsoft 365 Apps for Enterprise, Office 2019 and Office LTSC 2021, install the fixed build listed in the vendor release notes.
  5. Verify deployed Office build numbers across all endpoints and check systems for signs of compromise.

For Microsoft 365 Apps for Enterprise, Microsoft Office 2019 and Microsoft Office LTSC 2021, the CVE record names no fixed version. Consult the Microsoft advisory and release notes for the fixed build. CISA's required action is to apply updates per vendor instructions, so install the latest vendor-provided update for these products.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-357

Questions about CVE-2021-42292

Is CVE-2021-42292 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-17, with a US federal due date of 2021-12-01. Whether it is used in ransomware campaigns is unknown.
Can it be exploited remotely without user action?
The CVSS vector lists a local attack vector and requires user interaction, though no privileges are needed. CISA's SSVC rates it as not automatable.
Which version should we install for Office 2019 or Microsoft 365 Apps?
The CVE record names no fixed version for these products. It refers to builds before the fixed release, so check the vendor release notes and apply updates per vendor instructions.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.