Microsoft Exchange Server Remote Code Execution Vulnerability
CVE-2021-26855
Score elevated to 9.8 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 9.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
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 99(Act)EG Risk 99/100SSVC: Act
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 computedSeverity98% × 45%Exploitation100% × 40%Automatability100% × 15%Action: Fix now — active exploitation, automatable, high impact. - EPSS PROB
- 100%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
March 3, 2021
Last Modified
June 17, 2026
Advisory Details (5)
Auto-updated Jul 26, 2026Security 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-26855Packet Storm
http://packetstormsecurity.com/files/162736/Microsoft-Exchange-ProxyLogon-Collector.htmlPacket Storm
http://packetstormsecurity.com/files/162610/Microsoft-Exchange-2019-Unauthenticated-Email-Download.htmlWeakness Classification(1)
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 54× in last 7d / 346× 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 699 total refreshes for this CVE.
- 2026-07-28 04:00 UTCVendor advisory
- 2026-07-28 04:00 UTCGHSA enrichment
- 2026-07-28 00:11 UTCVendor advisory
- 2026-07-28 00:11 UTCGHSA enrichment
- 2026-07-27 20:23 UTCVendor advisory
- 2026-07-27 20:23 UTCGHSA enrichment
- 2026-07-27 19:24 UTCCISA KEV update
- 2026-07-27 17:17 UTCCISA KEV update
- 2026-07-27 16:33 UTCVendor advisory
- 2026-07-27 16:33 UTCGHSA enrichment
- 2026-07-27 12:44 UTCGHSA enrichment
- 2026-07-27 08:55 UTCVendor advisory
- 2026-07-27 08:55 UTCGHSA enrichment
- 2026-07-27 05:07 UTCVendor advisory
- 2026-07-27 05:07 UTCGHSA enrichment
- 2026-07-27 01:18 UTCVendor advisory
- 2026-07-27 01:18 UTCGHSA enrichment
- 2026-07-26 21:28 UTCVendor advisory
- 2026-07-26 21:28 UTCGHSA enrichment
- 2026-07-26 17:39 UTCVendor advisory
- 2026-07-26 17:39 UTCGHSA enrichment
- 2026-07-26 13:50 UTCEG score recompute
- 2026-07-26 13:50 UTCVendor advisory
- 2026-07-26 13:49 UTCGHSA enrichment
- 2026-07-26 09:59 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-26 09:59 UTCGHSA enrichment
- 2026-07-26 06:10 UTCVendor advisory
- 2026-07-26 06:10 UTCGHSA enrichment
- 2026-07-26 02:13 UTCVendor advisory
- 2026-07-26 02:13 UTCGHSA enrichment
- 2026-07-23 01:58 UTCEG score recompute
- 2026-07-22 23:14 UTCVendor advisory
- 2026-07-22 23:14 UTCGHSA enrichment
- 2026-07-22 22:45 UTCEG score recompute
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 19:23 UTCGHSA enrichment
- 2026-07-22 15:34 UTCVendor advisory
- 2026-07-22 15:34 UTCGHSA enrichment
- 2026-07-22 11:45 UTCVendor advisory
- 2026-07-22 11:45 UTCGHSA enrichment
- 2026-07-22 07:55 UTCEG score recompute
- 2026-07-22 07:55 UTCVendor advisory
- 2026-07-22 07:55 UTCGHSA enrichment
- 2026-07-22 04:06 UTCVendor advisory
- 2026-07-22 04:06 UTCGHSA enrichment
- 2026-07-22 00:08 UTCVendor advisory
- 2026-07-22 00:08 UTCGHSA enrichment
- 2026-07-21 18:14 UTCVendor advisory
- 2026-07-21 18:14 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 14:26 UTCVendor advisory
- 2026-07-21 14:26 UTCGHSA enrichment
- 2026-07-21 10:37 UTCVendor advisory
- 2026-07-21 10:36 UTCGHSA enrichment
- 2026-07-21 06:46 UTCVendor advisory
- 2026-07-21 06:46 UTCGHSA enrichment
- 2026-07-21 02:58 UTCVendor advisory
- 2026-07-21 02:58 UTCGHSA enrichment
- 2026-07-20 23:09 UTCVendor advisory
- 2026-07-20 23:09 UTCGHSA enrichment
- 2026-07-20 19:20 UTCVendor advisory
- 2026-07-20 19:20 UTCGHSA enrichment
- 2026-07-20 15:29 UTCGHSA enrichment
- 2026-07-20 11:40 UTCGHSA enrichment
- 2026-07-20 07:51 UTCVendor advisory
- 2026-07-20 07:50 UTCGHSA enrichment
- 2026-07-20 04:01 UTCVendor advisory
- 2026-07-20 04:01 UTCGHSA enrichment
- 2026-07-20 00:13 UTCVendor advisory
- 2026-07-20 00:12 UTCGHSA enrichment
- 2026-07-19 20:23 UTCVendor advisory
- 2026-07-19 20:23 UTCGHSA enrichment
- 2026-07-19 16:34 UTCVendor advisory
- 2026-07-19 16:34 UTCGHSA enrichment
- 2026-07-19 12:45 UTCVendor advisory
- 2026-07-19 12:44 UTCGHSA enrichment
- 2026-07-19 08:55 UTCVendor advisory
- 2026-07-19 08:55 UTCGHSA enrichment
- 2026-07-19 05:06 UTCVendor advisory
- 2026-07-19 05:06 UTCGHSA enrichment
- 2026-07-19 01:16 UTCGHSA enrichment
- 2026-07-18 21:25 UTCVendor advisory
- 2026-07-18 21:25 UTCGHSA enrichment
- 2026-07-18 17:36 UTCVendor advisory
- 2026-07-18 17:35 UTCGHSA enrichment
- 2026-07-18 13:47 UTCVendor advisory
- 2026-07-18 13:47 UTCGHSA enrichment
- 2026-07-18 09:58 UTCVendor advisory
- 2026-07-18 09:58 UTCGHSA enrichment
- 2026-07-18 06:09 UTCVendor advisory
- 2026-07-18 06:09 UTCGHSA enrichment
- 2026-07-18 02:18 UTCVendor advisory
- 2026-07-18 02:18 UTCGHSA enrichment
- 2026-07-17 22:29 UTCVendor advisory
- 2026-07-17 22:29 UTCGHSA enrichment
- 2026-07-17 18:40 UTCVendor advisory
- 2026-07-17 18:40 UTCGHSA enrichment
- 2026-07-17 14:51 UTCVendor advisory
- 2026-07-17 14:51 UTCGHSA enrichment
- 2026-07-17 11:02 UTCVendor advisory
Publicly available exploits
(10 references)Working exploit code is in the public domain (6 GitHub PoCs) (4 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-49895First seen May 21, 2021
Microsoft Exchange 2019 - Unauthenticated Email Download (Metasploit)
Open source ↗ - Exploit-DBEDB-49879First seen May 18, 2021
Microsoft Exchange 2019 - Unauthenticated Email Download
Open source ↗ - GitHub PoChosch3n/ProxyVulnsFirst seen Apr 14, 2021
[ProxyLogon] CVE-2021-26855 & CVE-2021-27065 Fixed RawIdentity Bug Exploit. [ProxyOracle] CVE-2021-31195 & CVE-2021-31196 Exploit Chains. [ProxyShell] CVE-2021-34473 & CVE-2021-34523 & CVE-2021-31207 Exploit Chains.
Open source ↗ - GitHub PoCFlangvik/SharpProxyLogonFirst seen Mar 29, 2021
C# POC for CVE-2021-26855 aka ProxyLogon, supports the classically semi-interactive web shell as well as shellcode injection
Open source ↗ - GitHub PoCpraetorian-inc/proxylogon-exploitFirst seen Mar 24, 2021
Proof-of-concept exploit for CVE-2021-26855 and CVE-2021-27065. Unauthenticated RCE in Exchange.
Open source ↗ - GitHub PoCp0wershe11/ProxyLogonFirst seen Mar 17, 2021
ProxyLogon(CVE-2021-26855+CVE-2021-27065) Exchange Server RCE(SSRF->GetWebShell)
Open source ↗ - Exploit-DBEDB-49663First seen Mar 14, 2021
Microsoft Exchange 2019 - Server-Side Request Forgery
Open source ↗ - Exploit-DBEDB-49637First seen Mar 11, 2021
Microsoft Exchange 2019 - Server-Side Request Forgery (Proxylogon) (PoC)
Open source ↗ - GitHub PoChackerschoice/CVE-2021-26855First seen Mar 11, 2021
PoC of proxylogon chain SSRF(CVE-2021-26855) to write file by testanull, censored by github
Open source ↗ - Open source ↗GitHub PoCalt3kx/CVE-2021-26855_PoCFirst seen Mar 10, 2021
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(6)
What is CVE-2021-26855?
When was CVE-2021-26855 disclosed?
Is CVE-2021-26855 actively exploited?
What is the CVSS score of CVE-2021-26855?
Which products are affected by CVE-2021-26855?
How do I remediate CVE-2021-26855?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2021-26855
Is Your Infrastructure Affected by CVE-2021-26855?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.