Microsoft Exchange Server Elevation of Privilege Vulnerability
CVE-2021-34523
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.0 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.0
- EG Score
- 9.8(high)
- EG Risk
- 84(Attend)EG Risk 84/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 computedSeverity98% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 100.0%
- KEV
- ⚠ Exploited
Published
July 14, 2021
Last Modified
October 30, 2025
Advisory Details (4)
Auto-updated Jun 1, 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-34523Security 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-34523Weakness 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 53× in last 7d / 347× 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 677 total refreshes for this CVE.
- 2026-07-23 02:01 UTCEG score recompute
- 2026-07-22 23:00 UTCVendor advisory
- 2026-07-22 23:00 UTCGHSA enrichment
- 2026-07-22 22:48 UTCEG score recompute
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 19:13 UTCGHSA enrichment
- 2026-07-22 15:24 UTCVendor advisory
- 2026-07-22 15:24 UTCGHSA enrichment
- 2026-07-22 11:36 UTCVendor advisory
- 2026-07-22 11:36 UTCGHSA enrichment
- 2026-07-22 07:47 UTCVendor advisory
- 2026-07-22 07:47 UTCGHSA enrichment
- 2026-07-22 04:00 UTCVendor advisory
- 2026-07-22 03:59 UTCGHSA enrichment
- 2026-07-22 00:01 UTCVendor advisory
- 2026-07-22 00:01 UTCGHSA enrichment
- 2026-07-21 18:07 UTCVendor advisory
- 2026-07-21 18:07 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 14:19 UTCVendor advisory
- 2026-07-21 14:19 UTCGHSA enrichment
- 2026-07-21 10:32 UTCVendor advisory
- 2026-07-21 10:31 UTCGHSA enrichment
- 2026-07-21 06:44 UTCVendor advisory
- 2026-07-21 06:44 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-21 02:56 UTCVendor advisory
- 2026-07-21 02:56 UTCGHSA enrichment
- 2026-07-20 23:09 UTCVendor advisory
- 2026-07-20 23:09 UTCGHSA enrichment
- 2026-07-20 19:21 UTCVendor advisory
- 2026-07-20 19:21 UTCGHSA enrichment
- 2026-07-20 15:33 UTCGHSA enrichment
- 2026-07-20 11:44 UTCGHSA enrichment
- 2026-07-20 07:57 UTCVendor advisory
- 2026-07-20 07:57 UTCGHSA enrichment
- 2026-07-20 04:10 UTCVendor advisory
- 2026-07-20 04:10 UTCGHSA enrichment
- 2026-07-20 00:23 UTCVendor advisory
- 2026-07-19 20:34 UTCVendor advisory
- 2026-07-19 20:34 UTCGHSA enrichment
- 2026-07-19 16:47 UTCVendor advisory
- 2026-07-19 16:47 UTCGHSA enrichment
- 2026-07-19 13:00 UTCVendor advisory
- 2026-07-19 13:00 UTCGHSA enrichment
- 2026-07-19 09:13 UTCVendor advisory
- 2026-07-19 09:13 UTCGHSA enrichment
- 2026-07-19 05:26 UTCVendor advisory
- 2026-07-19 05:26 UTCGHSA enrichment
- 2026-07-19 01:38 UTCGHSA enrichment
- 2026-07-18 21:51 UTCVendor advisory
- 2026-07-18 21:51 UTCGHSA enrichment
- 2026-07-18 18:03 UTCVendor advisory
- 2026-07-18 18:03 UTCGHSA enrichment
- 2026-07-18 14:15 UTCVendor advisory
- 2026-07-18 14:15 UTCGHSA enrichment
- 2026-07-18 10:27 UTCVendor advisory
- 2026-07-18 10:27 UTCGHSA enrichment
- 2026-07-18 06:40 UTCVendor advisory
- 2026-07-18 06:40 UTCGHSA enrichment
- 2026-07-18 02:53 UTCVendor advisory
- 2026-07-18 02:53 UTCGHSA enrichment
- 2026-07-17 23:06 UTCVendor advisory
- 2026-07-17 23:06 UTCGHSA enrichment
- 2026-07-17 19:19 UTCVendor advisory
- 2026-07-17 19:19 UTCGHSA enrichment
- 2026-07-17 15:32 UTCVendor advisory
- 2026-07-17 15:32 UTCGHSA enrichment
- 2026-07-17 11:44 UTCVendor advisory
- 2026-07-17 11:44 UTCGHSA enrichment
- 2026-07-17 07:56 UTCEG score recompute
- 2026-07-17 07:56 UTCVendor advisory
- 2026-07-17 07:56 UTCGHSA enrichment
- 2026-07-17 04:09 UTCVendor advisory
- 2026-07-17 04:09 UTCGHSA enrichment
- 2026-07-17 00:21 UTCVendor advisory
- 2026-07-17 00:21 UTCGHSA enrichment
- 2026-07-16 20:34 UTCVendor advisory
- 2026-07-16 20:34 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 16:46 UTCGHSA enrichment
- 2026-07-16 12:49 UTCVendor advisory
- 2026-07-16 12:49 UTCGHSA enrichment
- 2026-07-16 09:02 UTCVendor advisory
- 2026-07-16 09:02 UTCGHSA enrichment
- 2026-07-16 05:15 UTCVendor advisory
- 2026-07-16 05:15 UTCGHSA enrichment
- 2026-07-16 01:27 UTCVendor advisory
- 2026-07-16 01:27 UTCGHSA enrichment
- 2026-07-15 21:40 UTCVendor advisory
- 2026-07-15 21:39 UTCGHSA enrichment
- 2026-07-15 17:52 UTCVendor advisory
- 2026-07-15 17:52 UTCGHSA enrichment
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 14:04 UTCVendor advisory
- 2026-07-15 14:04 UTCGHSA enrichment
- 2026-07-15 10:15 UTCVendor advisory
- 2026-07-15 10:15 UTCGHSA enrichment
- 2026-07-15 06:28 UTCVendor advisory
- 2026-07-15 06:27 UTCGHSA enrichment
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.
- GitHub PoCSUPRAAA-1337/CVE-2021-34523First seen Sep 2, 2023
test-yaml
Open source ↗ - GitHub PoCmithridates1313/ProxyShell_POCFirst seen Oct 2, 2021
POC for scanning ProxyShell(CVE-2021-34523,CVE-2021-34473,CVE-2021-31207)
Open source ↗ - Metasploitexploit/windows/http/exchange_proxyshell_rce✓ verifiedFirst seen Apr 6, 2021
Microsoft Exchange ProxyShell RCE
Open source ↗
Frequently asked(6)
What is CVE-2021-34523?
When was CVE-2021-34523 disclosed?
Is CVE-2021-34523 actively exploited?
What is the CVSS score of CVE-2021-34523?
Which products are affected by CVE-2021-34523?
How do I remediate CVE-2021-34523?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2021-34523
Is Your Infrastructure Affected by CVE-2021-34523?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.