Microsoft Exchange Server Remote Code Execution Vulnerability
CVE-2021-42321
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-17), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 92%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
November 10, 2021
Last Modified
August 19, 2026
Advisory Details (4)
Auto-updated Jun 2, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-42321Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-42321Vendor Advisories for CVE-2021-42321(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 84× in last 7d / 369× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,172 total refreshes for this CVE.
- 2026-09-08 09:37 UTCVendor advisory
- 2026-09-08 09:36 UTCGHSA enrichment
- 2026-09-08 09:35 UTCGHSA enrichment
- 2026-09-08 05:14 UTCVendor advisory
- 2026-09-08 05:14 UTCGHSA enrichment
- 2026-09-08 00:58 UTCVendor advisory
- 2026-09-08 00:58 UTCGHSA enrichment
- 2026-09-07 20:42 UTCVendor advisory
- 2026-09-07 20:42 UTCGHSA enrichment
- 2026-09-07 16:26 UTCVendor advisory
- 2026-09-07 16:26 UTCGHSA enrichment
- 2026-09-07 12:10 UTCVendor advisory
- 2026-09-07 12:10 UTCGHSA enrichment
- 2026-09-07 07:54 UTCVendor advisory
- 2026-09-07 07:54 UTCGHSA enrichment
- 2026-09-07 03:34 UTCVendor advisory
- 2026-09-07 03:34 UTCGHSA enrichment
- 2026-09-06 23:16 UTCVendor advisory
- 2026-09-06 23:16 UTCGHSA enrichment
- 2026-09-06 19:01 UTCVendor advisory
- 2026-09-06 19:01 UTCGHSA enrichment
- 2026-09-06 14:45 UTCEG score recompute
- 2026-09-06 14:45 UTCVendor advisory
- 2026-09-06 14:45 UTCGHSA enrichment
- 2026-09-06 13:45 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-06 10:29 UTCVendor advisory
- 2026-09-06 10:29 UTCGHSA enrichment
- 2026-09-06 06:13 UTCVendor advisory
- 2026-09-06 06:13 UTCGHSA enrichment
- 2026-09-06 01:57 UTCVendor advisory
- 2026-09-06 01:57 UTCGHSA enrichment
- 2026-09-05 21:41 UTCVendor advisory
- 2026-09-05 21:41 UTCGHSA enrichment
- 2026-09-05 17:26 UTCEG score recompute
- 2026-09-05 17:26 UTCVendor advisory
- 2026-09-05 17:25 UTCGHSA enrichment
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 13:10 UTCVendor advisory
- 2026-09-05 13:10 UTCGHSA enrichment
- 2026-09-05 08:53 UTCVendor advisory
- 2026-09-05 08:53 UTCGHSA enrichment
- 2026-09-05 04:37 UTCVendor advisory
- 2026-09-05 04:37 UTCGHSA enrichment
- 2026-09-05 00:21 UTCVendor advisory
- 2026-09-05 00:21 UTCGHSA enrichment
- 2026-09-04 20:05 UTCVendor advisory
- 2026-09-04 20:05 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 15:49 UTCVendor advisory
- 2026-09-04 15:49 UTCGHSA enrichment
- 2026-09-04 11:33 UTCVendor advisory
- 2026-09-04 11:33 UTCGHSA enrichment
- 2026-09-04 07:17 UTCVendor advisory
- 2026-09-04 07:17 UTCGHSA enrichment
- 2026-09-04 03:01 UTCVendor advisory
- 2026-09-04 03:01 UTCGHSA enrichment
- 2026-09-03 22:44 UTCVendor advisory
- 2026-09-03 22:44 UTCGHSA enrichment
- 2026-09-03 18:25 UTCVendor advisory
- 2026-09-03 18:25 UTCGHSA enrichment
- 2026-09-03 14:06 UTCVendor advisory
- 2026-09-03 14:05 UTCGHSA enrichment
- 2026-09-03 09:46 UTCVendor advisory
- 2026-09-03 09:46 UTCGHSA enrichment
- 2026-09-03 05:30 UTCVendor advisory
- 2026-09-03 05:30 UTCGHSA enrichment
- 2026-09-03 01:14 UTCVendor advisory
- 2026-09-03 01:14 UTCGHSA enrichment
- 2026-09-02 20:58 UTCVendor advisory
- 2026-09-02 20:57 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 16:41 UTCVendor advisory
- 2026-09-02 16:41 UTCGHSA enrichment
- 2026-09-02 12:25 UTCVendor advisory
- 2026-09-02 12:25 UTCGHSA enrichment
- 2026-09-02 08:09 UTCGHSA enrichment
- 2026-09-02 03:53 UTCVendor advisory
- 2026-09-02 03:52 UTCGHSA enrichment
- 2026-09-01 23:36 UTCVendor advisory
- 2026-09-01 23:36 UTCGHSA enrichment
- 2026-09-01 19:21 UTCVendor advisory
- 2026-09-01 19:20 UTCGHSA enrichment
- 2026-09-01 15:00 UTCVendor advisory
- 2026-09-01 14:59 UTCGHSA enrichment
- 2026-09-01 10:40 UTCVendor advisory
- 2026-09-01 10:40 UTCGHSA enrichment
- 2026-09-01 06:25 UTCVendor advisory
- 2026-09-01 06:24 UTCGHSA enrichment
- 2026-09-01 02:08 UTCVendor advisory
- 2026-09-01 02:08 UTCGHSA enrichment
- 2026-08-31 21:49 UTCVendor advisory
- 2026-08-31 21:49 UTCGHSA enrichment
- 2026-08-31 17:34 UTCVendor advisory
- 2026-08-31 17:34 UTCGHSA enrichment
- 2026-08-31 14:19 UTCCISA KEV update
- 2026-08-31 13:16 UTCVendor advisory
- 2026-08-31 13:15 UTCGHSA enrichment
- 2026-08-31 08:56 UTCVendor advisory
- 2026-08-31 08:56 UTCGHSA enrichment
- 2026-08-31 04:41 UTCVendor advisory
Publicly available exploits
(3 references)Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Open source ↗GitHub PoC7BitsTeam/exch_CVE-2021-42321First seen Oct 8, 2022
- Metasploitexploit/windows/http/exchange_chainedserializationbinder_rce✓ verifiedFirst seen Dec 9, 2021
Microsoft Exchange Server ChainedSerializationBinder RCE
Open source ↗ - GitHub PoCDarkSprings/CVE-2021-42321First seen Nov 23, 2021
Microsoft Exchange Server Poc
Open source ↗
Frequently asked(6)
What is CVE-2021-42321?
When was CVE-2021-42321 disclosed?
Is CVE-2021-42321 actively exploited?
What is the CVSS score of CVE-2021-42321?
Which products are affected by CVE-2021-42321?
How do I remediate CVE-2021-42321?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2021-42321
Is Your Infrastructure Affected by CVE-2021-42321?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.