CVE-2021-42321
🟠 Medium In CISA KEVMicrosoft Exchange Server (on-premises). Exchange Online was never affected. Not part of the ProxyLogon set, despite also being an Exchange RCE · 2016 CU21 before 15.01.2308.020 ; 2016 CU22 before 15.01.2375.017 ; 2019 CU10 before 15.02.0792.019 ; 2019 CU11 before 15.02.0986.014
CVSS (Koffei note)
8.8CVSS (v3.1, CVE List)
8.8EPSS (2026-11-18)
91.737%99.82th percentile
CISA KEV
2021-11-17due 2021-12-01
Exploitation
Yes — CISA KEV since 17/11/2021, SSVC exploitation active, automatable no, technical impact total (recorded 03/01/2024). Disclosed on 09/11/2021 and in KEV eight days later, which is unusually fast. Because it is post-authentication, it is a second-stage flaw: it turns any compromised mailbox into code execution on the Exchange server. No dated incident was read for this row. Not dated inside this report's 60-day window: nothing read for this row evidences exploitation after the KEV entry of 17/11/2021, and the fix has been available for years, so this is 🟠 and not 🔴 under the recency rule. Neither CISA KEV nor its JSON feed could be reached in this run, so the KEV date comes from the record's CISA-ADP container.
Timeline
- 10/11/2021CVE record published (CVE List)
- 17/11/2021Added to the CISA KEV catalogue
- 01/12/2021CISA deadline for US federal agencies
Risk
8.8 High (v3.1, Microsoft CNA, temporal E:U/RL:O/RC:C — note E:U, unproven, which the subsequent KEV entry contradicts) — AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, EPSS 91.737% (99.82nd percentile, scored 05/11/2026) (CISA-ADP recorded CWE-noinfo ; the record gives only "Remote Code Execution". PR:L, so it needs a valid mailbox, which is what distinguishes it from ProxyLogon)
Fix
Yes — November 2021 Patch Tuesday (09/11/2021)
Official description
Microsoft Exchange Server Remote Code Execution Vulnerability
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C