Microsoft Exchange Server Remote Code Execution Vulnerability
CVE-2021-26857
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.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
- 7.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
- 99.8%
- KEV
- ⚠ Exploited
Published
March 3, 2021
Last Modified
December 18, 2025
Advisory Details (2)
Auto-updated Jun 3, 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-26857Security 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-26857Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
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 83× in last 7d / 349× 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 637 total refreshes for this CVE.
- 2026-07-23 01:58 UTCEG score recompute
- 2026-07-22 23:29 UTCEG score recompute
- 2026-07-22 23:29 UTCVendor advisory
- 2026-07-22 23:28 UTCGHSA enrichment
- 2026-07-22 22:45 UTCEG score recompute
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 19:10 UTCGHSA enrichment
- 2026-07-22 14:52 UTCEG score recompute
- 2026-07-22 14:52 UTCVendor advisory
- 2026-07-22 14:52 UTCGHSA enrichment
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 10:33 UTCVendor advisory
- 2026-07-22 10:33 UTCGHSA enrichment
- 2026-07-22 06:14 UTCVendor advisory
- 2026-07-22 06:14 UTCGHSA enrichment
- 2026-07-22 01:56 UTCVendor advisory
- 2026-07-22 01:56 UTCGHSA enrichment
- 2026-07-21 21:38 UTCVendor advisory
- 2026-07-21 21:38 UTCGHSA enrichment
- 2026-07-21 17:19 UTCVendor advisory
- 2026-07-21 17:19 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 13:01 UTCVendor advisory
- 2026-07-21 13:01 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-21 08:44 UTCVendor advisory
- 2026-07-21 08:43 UTCGHSA enrichment
- 2026-07-21 04:24 UTCVendor advisory
- 2026-07-21 04:23 UTCGHSA enrichment
- 2026-07-21 00:04 UTCVendor advisory
- 2026-07-21 00:04 UTCGHSA enrichment
- 2026-07-20 19:46 UTCVendor advisory
- 2026-07-20 19:45 UTCGHSA enrichment
- 2026-07-20 15:27 UTCGHSA enrichment
- 2026-07-20 11:07 UTCGHSA enrichment
- 2026-07-20 06:49 UTCVendor advisory
- 2026-07-20 06:49 UTCGHSA enrichment
- 2026-07-20 02:32 UTCVendor advisory
- 2026-07-20 02:32 UTCGHSA enrichment
- 2026-07-19 22:13 UTCVendor advisory
- 2026-07-19 22:13 UTCGHSA enrichment
- 2026-07-19 17:55 UTCVendor advisory
- 2026-07-19 17:55 UTCGHSA enrichment
- 2026-07-19 13:37 UTCVendor advisory
- 2026-07-19 13:37 UTCGHSA enrichment
- 2026-07-19 09:20 UTCVendor advisory
- 2026-07-19 09:20 UTCGHSA enrichment
- 2026-07-19 05:02 UTCVendor advisory
- 2026-07-19 05:02 UTCGHSA enrichment
- 2026-07-19 00:43 UTCGHSA enrichment
- 2026-07-18 20:24 UTCVendor advisory
- 2026-07-18 20:24 UTCGHSA enrichment
- 2026-07-18 16:06 UTCVendor advisory
- 2026-07-18 16:06 UTCGHSA enrichment
- 2026-07-18 11:48 UTCVendor advisory
- 2026-07-18 11:48 UTCGHSA enrichment
- 2026-07-18 07:30 UTCVendor advisory
- 2026-07-18 07:30 UTCGHSA enrichment
- 2026-07-18 03:12 UTCVendor advisory
- 2026-07-18 03:12 UTCGHSA enrichment
- 2026-07-17 22:54 UTCVendor advisory
- 2026-07-17 22:54 UTCGHSA enrichment
- 2026-07-17 18:36 UTCVendor advisory
- 2026-07-17 18:36 UTCGHSA enrichment
- 2026-07-17 14:18 UTCVendor advisory
- 2026-07-17 14:18 UTCGHSA enrichment
- 2026-07-17 10:00 UTCEG score recompute
- 2026-07-17 10:00 UTCVendor advisory
- 2026-07-17 10:00 UTCGHSA enrichment
- 2026-07-17 05:42 UTCVendor advisory
- 2026-07-17 05:42 UTCGHSA enrichment
- 2026-07-17 01:24 UTCVendor advisory
- 2026-07-17 01:24 UTCGHSA enrichment
- 2026-07-16 21:06 UTCVendor advisory
- 2026-07-16 21:05 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 16:46 UTCGHSA enrichment
- 2026-07-16 12:23 UTCVendor advisory
- 2026-07-16 12:23 UTCGHSA enrichment
- 2026-07-16 08:04 UTCVendor advisory
- 2026-07-16 08:04 UTCGHSA enrichment
- 2026-07-16 03:47 UTCVendor advisory
- 2026-07-16 03:47 UTCGHSA enrichment
- 2026-07-15 23:29 UTCVendor advisory
- 2026-07-15 23:29 UTCGHSA enrichment
- 2026-07-15 19:11 UTCVendor advisory
- 2026-07-15 19:11 UTCGHSA enrichment
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 14:53 UTCVendor advisory
- 2026-07-15 14:53 UTCGHSA enrichment
- 2026-07-15 10:35 UTCVendor advisory
- 2026-07-15 10:35 UTCGHSA enrichment
- 2026-07-15 06:17 UTCVendor advisory
- 2026-07-15 06:16 UTCGHSA enrichment
- 2026-07-15 01:59 UTCGHSA enrichment
- 2026-07-14 21:41 UTCVendor advisory
- 2026-07-14 21:41 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCsirpedrotavares/Proxylogon-exploitFirst seen Mar 11, 2021
proxylogon exploit - CVE-2021-26857
Open source ↗
Frequently asked(6)
What is CVE-2021-26857?
When was CVE-2021-26857 disclosed?
Is CVE-2021-26857 actively exploited?
What is the CVSS score of CVE-2021-26857?
Which products are affected by CVE-2021-26857?
How do I remediate CVE-2021-26857?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2021-26857
Is Your Infrastructure Affected by CVE-2021-26857?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.