Cyber Resilience

CVE-2022-21841

HighUpdated

Published: 11 January 2022

Published
11 January 2022
Modified
19 May 2026
KEV Added
Patch
CVSS Score v3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0416 88.9th percentile
Risk Priority 18 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2022-21841 is a high-severity an unspecified weakness vulnerability in Microsoft Office. Its CVSS base score is 7.8 (High).

Operationally, ranked in the top 11.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis

Microsoft Excel contains a remote code execution vulnerability that allows an attacker to execute arbitrary code on an affected system. The flaw affects Microsoft Excel and carries a CVSS 3.1 score of 7.8 with an attack vector of local access, low complexity, no privileges required, and user interaction needed to trigger the issue, resulting in high impact to confidentiality, integrity, and availability.

An attacker can exploit the vulnerability by supplying a specially crafted Excel file that, once opened by a victim, leads to code execution in the context of the current user. This enables full compromise of the affected workstation, including data theft, persistence, or further lateral movement within an environment.

Microsoft has published security updates and guidance addressing the issue through its Security Response Center advisories. The EPSS score for the vulnerability rose materially from a low baseline to a peak of 0.1804 on 2025-01-22 before receding to the current value of 0.0416, indicating a later surge in observed exploitation interest after initial disclosure.

EU & UK References

Vulnerability details

Microsoft Excel Remote Code Execution Vulnerability

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

microsoft
365 apps
all versions
microsoft
office
2013, 2016, 2019
microsoft
office long term servicing channel
2021

Mitigating Controls

No mitigating controls mapped yet. The per-CVE control annotator has not reached this CVE.

References