Microsoft Exchange Server Security Feature Bypass Vulnerability
CVE-2021-31207
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 6.6 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
- 6.6
- 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
- 100.0%
- KEV
- ⚠ Exploited
Published
May 11, 2021
Last Modified
October 30, 2025
Advisory Details (4)
Auto-updated Jun 12, 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-31207ZDI-21-819 - TrendAI™ Zero Day Initiative™ (ZDI)
https://www.zerodayinitiative.com/advisories/ZDI-21-819/Security 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-31207Weakness 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 67× in last 7d / 343× 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 634 total refreshes for this CVE.
- 2026-07-23 02:00 UTCEG score recompute
- 2026-07-22 21:52 UTCEG score recompute
- 2026-07-22 21:52 UTCVendor advisory
- 2026-07-22 21:52 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 17:39 UTCGHSA enrichment
- 2026-07-22 13:27 UTCVendor advisory
- 2026-07-22 13:27 UTCGHSA enrichment
- 2026-07-22 09:15 UTCVendor advisory
- 2026-07-22 09:15 UTCGHSA enrichment
- 2026-07-22 05:03 UTCVendor advisory
- 2026-07-22 05:03 UTCGHSA enrichment
- 2026-07-22 00:49 UTCVendor advisory
- 2026-07-22 00:48 UTCGHSA enrichment
- 2026-07-21 20:36 UTCVendor advisory
- 2026-07-21 20:36 UTCGHSA enrichment
- 2026-07-21 16:22 UTCVendor advisory
- 2026-07-21 16:22 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 12:11 UTCVendor advisory
- 2026-07-21 12:11 UTCGHSA enrichment
- 2026-07-21 07:59 UTCVendor advisory
- 2026-07-21 07:59 UTCGHSA enrichment
- 2026-07-21 03:47 UTCVendor advisory
- 2026-07-21 03:47 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-20 23:34 UTCVendor advisory
- 2026-07-20 23:34 UTCGHSA enrichment
- 2026-07-20 19:23 UTCVendor advisory
- 2026-07-20 19:23 UTCGHSA enrichment
- 2026-07-20 15:11 UTCGHSA enrichment
- 2026-07-20 10:58 UTCGHSA enrichment
- 2026-07-20 06:46 UTCVendor advisory
- 2026-07-20 06:46 UTCGHSA enrichment
- 2026-07-20 02:17 UTCVendor advisory
- 2026-07-20 02:17 UTCGHSA enrichment
- 2026-07-19 22:05 UTCVendor advisory
- 2026-07-19 22:05 UTCGHSA enrichment
- 2026-07-19 17:53 UTCVendor advisory
- 2026-07-19 17:53 UTCGHSA enrichment
- 2026-07-19 13:41 UTCVendor advisory
- 2026-07-19 13:41 UTCGHSA enrichment
- 2026-07-19 09:29 UTCVendor advisory
- 2026-07-19 09:29 UTCGHSA enrichment
- 2026-07-19 05:17 UTCVendor advisory
- 2026-07-19 05:17 UTCGHSA enrichment
- 2026-07-19 01:04 UTCGHSA enrichment
- 2026-07-18 20:52 UTCVendor advisory
- 2026-07-18 20:52 UTCGHSA enrichment
- 2026-07-18 16:40 UTCVendor advisory
- 2026-07-18 16:40 UTCGHSA enrichment
- 2026-07-18 12:28 UTCVendor advisory
- 2026-07-18 12:28 UTCGHSA enrichment
- 2026-07-18 08:16 UTCVendor advisory
- 2026-07-18 08:16 UTCGHSA enrichment
- 2026-07-18 04:04 UTCVendor advisory
- 2026-07-18 04:04 UTCGHSA enrichment
- 2026-07-17 23:52 UTCVendor advisory
- 2026-07-17 23:52 UTCGHSA enrichment
- 2026-07-17 19:40 UTCVendor advisory
- 2026-07-17 19:40 UTCGHSA enrichment
- 2026-07-17 15:28 UTCVendor advisory
- 2026-07-17 15:28 UTCGHSA enrichment
- 2026-07-17 11:16 UTCVendor advisory
- 2026-07-17 11:16 UTCGHSA enrichment
- 2026-07-17 07:04 UTCEG score recompute
- 2026-07-17 07:04 UTCVendor advisory
- 2026-07-17 07:04 UTCGHSA enrichment
- 2026-07-17 02:52 UTCVendor advisory
- 2026-07-17 02:51 UTCGHSA enrichment
- 2026-07-16 22:39 UTCVendor advisory
- 2026-07-16 22:39 UTCGHSA enrichment
- 2026-07-16 18:27 UTCVendor advisory
- 2026-07-16 18:27 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 14:14 UTCVendor advisory
- 2026-07-16 14:14 UTCGHSA enrichment
- 2026-07-16 10:03 UTCVendor advisory
- 2026-07-16 10:02 UTCGHSA enrichment
- 2026-07-16 05:50 UTCVendor advisory
- 2026-07-16 05:50 UTCGHSA enrichment
- 2026-07-16 01:38 UTCVendor advisory
- 2026-07-16 01:38 UTCGHSA enrichment
- 2026-07-15 21:26 UTCVendor advisory
- 2026-07-15 21:26 UTCGHSA enrichment
- 2026-07-15 17:14 UTCVendor advisory
- 2026-07-15 17:14 UTCGHSA enrichment
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 13:02 UTCVendor advisory
- 2026-07-15 13:02 UTCGHSA enrichment
- 2026-07-15 08:47 UTCVendor advisory
- 2026-07-15 08:46 UTCGHSA enrichment
- 2026-07-15 04:32 UTCVendor advisory
- 2026-07-15 04:32 UTCGHSA enrichment
- 2026-07-15 00:17 UTCVendor advisory
- 2026-07-15 00:17 UTCGHSA enrichment
- 2026-07-14 20:06 UTCVendor advisory
- 2026-07-14 20:05 UTCGHSA enrichment
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 15:50 UTCVendor advisory
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Metasploitexploit/windows/http/exchange_proxyshell_rce✓ verifiedFirst seen Apr 6, 2021
Microsoft Exchange ProxyShell RCE
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Frequently asked(6)
What is CVE-2021-31207?
When was CVE-2021-31207 disclosed?
Is CVE-2021-31207 actively exploited?
What is the CVSS score of CVE-2021-31207?
Which products are affected by CVE-2021-31207?
How do I remediate CVE-2021-31207?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2021-31207
Is Your Infrastructure Affected by CVE-2021-31207?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.