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 PROB
- 100%
- EPSS %ILE
- 100%
- 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 84× in last 7d / 355× 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,296 total refreshes for this CVE.
- 2026-09-20 16:36 UTCVendor advisory
- 2026-09-20 16:36 UTCGHSA enrichment
- 2026-09-20 12:25 UTCVendor advisory
- 2026-09-20 12:24 UTCGHSA enrichment
- 2026-09-20 08:10 UTCVendor advisory
- 2026-09-20 08:10 UTCGHSA enrichment
- 2026-09-20 03:59 UTCVendor advisory
- 2026-09-20 03:59 UTCGHSA enrichment
- 2026-09-19 23:47 UTCVendor advisory
- 2026-09-19 23:47 UTCGHSA enrichment
- 2026-09-19 19:35 UTCVendor advisory
- 2026-09-19 19:35 UTCGHSA enrichment
- 2026-09-19 15:23 UTCVendor advisory
- 2026-09-19 15:23 UTCGHSA enrichment
- 2026-09-19 11:11 UTCVendor advisory
- 2026-09-19 11:11 UTCGHSA enrichment
- 2026-09-19 06:59 UTCVendor advisory
- 2026-09-19 06:59 UTCGHSA enrichment
- 2026-09-19 02:46 UTCVendor advisory
- 2026-09-19 02:46 UTCGHSA enrichment
- 2026-09-18 22:35 UTCVendor advisory
- 2026-09-18 22:35 UTCGHSA enrichment
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 18:23 UTCVendor advisory
- 2026-09-18 18:23 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 14:11 UTCVendor advisory
- 2026-09-18 14:11 UTCGHSA enrichment
- 2026-09-18 09:59 UTCVendor advisory
- 2026-09-18 09:59 UTCGHSA enrichment
- 2026-09-18 05:47 UTCVendor advisory
- 2026-09-18 05:47 UTCGHSA enrichment
- 2026-09-18 01:35 UTCVendor advisory
- 2026-09-18 01:35 UTCGHSA enrichment
- 2026-09-17 21:23 UTCVendor advisory
- 2026-09-17 21:23 UTCGHSA enrichment
- 2026-09-17 17:12 UTCVendor advisory
- 2026-09-17 17:12 UTCGHSA enrichment
- 2026-09-17 12:51 UTCVendor advisory
- 2026-09-17 12:51 UTCGHSA enrichment
- 2026-09-17 08:36 UTCVendor advisory
- 2026-09-17 08:36 UTCGHSA enrichment
- 2026-09-17 04:24 UTCVendor advisory
- 2026-09-17 04:24 UTCGHSA enrichment
- 2026-09-17 00:12 UTCVendor advisory
- 2026-09-17 00:12 UTCGHSA enrichment
- 2026-09-16 20:00 UTCVendor advisory
- 2026-09-16 20:00 UTCGHSA enrichment
- 2026-09-16 15:48 UTCVendor advisory
- 2026-09-16 15:48 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 11:36 UTCVendor advisory
- 2026-09-16 11:35 UTCGHSA enrichment
- 2026-09-16 07:21 UTCVendor advisory
- 2026-09-16 07:21 UTCGHSA enrichment
- 2026-09-16 03:09 UTCVendor advisory
- 2026-09-16 03:09 UTCGHSA enrichment
- 2026-09-15 22:57 UTCVendor advisory
- 2026-09-15 22:57 UTCGHSA enrichment
- 2026-09-15 18:45 UTCVendor advisory
- 2026-09-15 18:45 UTCGHSA enrichment
- 2026-09-15 14:33 UTCVendor advisory
- 2026-09-15 14:33 UTCGHSA enrichment
- 2026-09-15 10:21 UTCVendor advisory
- 2026-09-15 10:21 UTCGHSA enrichment
- 2026-09-15 06:09 UTCVendor advisory
- 2026-09-15 06:09 UTCGHSA enrichment
- 2026-09-15 01:57 UTCVendor advisory
- 2026-09-15 01:57 UTCGHSA enrichment
- 2026-09-14 21:45 UTCVendor advisory
- 2026-09-14 21:45 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 17:33 UTCVendor advisory
- 2026-09-14 17:33 UTCGHSA enrichment
- 2026-09-14 13:21 UTCVendor advisory
- 2026-09-14 13:21 UTCGHSA enrichment
- 2026-09-14 09:08 UTCVendor advisory
- 2026-09-14 09:08 UTCGHSA enrichment
- 2026-09-14 04:56 UTCVendor advisory
- 2026-09-14 04:56 UTCGHSA enrichment
- 2026-09-14 00:45 UTCVendor advisory
- 2026-09-14 00:45 UTCGHSA enrichment
- 2026-09-13 20:33 UTCVendor advisory
- 2026-09-13 20:33 UTCGHSA enrichment
- 2026-09-13 16:21 UTCVendor advisory
- 2026-09-13 16:21 UTCGHSA enrichment
- 2026-09-13 12:09 UTCVendor advisory
- 2026-09-13 12:09 UTCGHSA enrichment
- 2026-09-13 07:56 UTCVendor advisory
- 2026-09-13 07:56 UTCGHSA enrichment
- 2026-09-13 03:45 UTCVendor advisory
- 2026-09-13 03:45 UTCGHSA enrichment
- 2026-09-12 23:32 UTCVendor advisory
- 2026-09-12 23:32 UTCGHSA enrichment
- 2026-09-12 19:20 UTCVendor advisory
- 2026-09-12 19:20 UTCGHSA enrichment
- 2026-09-12 15:08 UTCVendor advisory
- 2026-09-12 15:08 UTCGHSA enrichment
- 2026-09-12 10:56 UTCVendor advisory
- 2026-09-12 10:56 UTCGHSA enrichment
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 CWE)
Same CWE
10 shownCWE-22 · CWE-434
- CVE-2026-9102EG 9.4CRITICAL
- CVE-2026-85706EG 10.0 KEVEPSS p96CRITICAL
- CVE-2026-84147EG 10.0CRITICAL
- CVE-2026-81780EG 10.0CRITICAL
- CVE-2026-82970EG 10.0CRITICAL
- CVE-2026-75949EG 10.0CRITICAL
- CVE-2026-74803EG 10.0CRITICAL
- CVE-2026-66665EG 10.0CRITICAL
- CVE-2026-61424EG 10.0CRITICAL
- CVE-2026-61900EG 10.0CRITICAL
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.