vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2021-42292

Microsoft Excel Security Feature Bypass Vulnerability

HIGH
7.8
CVSS Score
Published: November 10, 2021 at 12:47 AM UTC
Updated: August 19, 2026 at 07:35 PM UTC
7 products affected across 1 vendorOffice365 AppsOffice 2021

Using Microsoft Office 2019 by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft Office 2019 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH7.8
Exploitation
CISA KEV
Exploit prediction
EPSS 43%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score43.0%

EPSS (Exploit Prediction Scoring System) estimates a 43.0% chance this CVE is exploited in the wild within the next 30 days — higher than 99% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

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

Required Action
Apply updates per vendor instructions.
Ransomware Use
Unknown
Added to KEV
Nov 17, 2021
Remediation Due
Dec 1, 2021
1794 days overdue
Notes
https://nvd.nist.gov/vuln/detail/CVE-2021-42292

Description

Microsoft Excel Security Feature Bypass Vulnerability

Affected

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

365 Apps· Microsoft
95%
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
Excel· Microsoft
95%
15.0.0.0 ≤ v < 15.0.5397.100116.0.0.0 ≤ v < 16.0.5239.100115.0.0.016.0.0.02013 sp12016
Affected range stops below 15.0.5397.1001, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.0.5239.1001, so it looks safe — our inference, not a vendor statement
Office· Microsoft
95%
2013 sp12019
Office 2016· Microsoft
95%
16.0.0 ≤ v < 16.0.5239.100116.0.0
Affected range stops below 16.0.5239.1001, so it looks safe — our inference, not a vendor statement
Office 2019· Microsoft
95%
16.0.0 ≤ v < 16.55.2111140019.0.0 ≤ v < https://aka.ms/OfficeSecurityReleases16.0.019.0.0
Affected range stops below 16.55.21111400, so it looks safe — our inference, not a vendor statement
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
Office 2021· Microsoft
95%
16.0.1 ≤ v < 16.55.2111140016.0.1 ≤ v < https://aka.ms/OfficeSecurityReleases16.0.1
Affected range stops below 16.55.21111400, so it looks safe — our inference, not a vendor statement
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
Office 2013· Microsoft
60%
15.0.0 ≤ v < 15.0.5397.100115.0.0
Affected range stops below 15.0.5397.1001, 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:

Patch and advisory references

References (3)

PatchVendor Advisory
Source: [email protected]
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-42292
Vendor AdvisoryPatch
Source: cverecord
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-42292
US Government Resource
Source: 134c704f-9b21-4f2e-91b3-4a467353bcc0
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-42292

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-Other

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.

Create accountSign in
Free plan, no card