Microsoft Exchange Server Information Disclosure Vulnerability
CVE-2021-33766
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-01-18), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.3 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.3
- EG Score
- 9.0(high)
- EG Risk
- 96(Attend)EG Risk 96/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%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 98%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
July 14, 2021
Last Modified
October 29, 2025
Advisory Details (3)
Auto-updated Jun 11, 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-33766Security 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-33766Weakness 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 59× 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 723 total refreshes for this CVE.
- 2026-07-29 22:58 UTCVendor advisory
- 2026-07-29 22:58 UTCGHSA enrichment
- 2026-07-29 19:27 UTCCISA KEV update
- 2026-07-29 18:57 UTCVendor advisory
- 2026-07-29 18:57 UTCGHSA enrichment
- 2026-07-29 14:57 UTCVendor advisory
- 2026-07-29 14:57 UTCGHSA enrichment
- 2026-07-29 10:58 UTCVendor advisory
- 2026-07-29 10:58 UTCGHSA enrichment
- 2026-07-29 06:59 UTCVendor advisory
- 2026-07-29 06:59 UTCGHSA enrichment
- 2026-07-29 02:58 UTCVendor advisory
- 2026-07-29 02:58 UTCGHSA enrichment
- 2026-07-28 22:59 UTCVendor advisory
- 2026-07-28 22:59 UTCGHSA enrichment
- 2026-07-28 18:59 UTCVendor advisory
- 2026-07-28 18:59 UTCGHSA enrichment
- 2026-07-28 14:57 UTCVendor advisory
- 2026-07-28 14:57 UTCGHSA enrichment
- 2026-07-28 10:57 UTCVendor advisory
- 2026-07-28 10:57 UTCGHSA enrichment
- 2026-07-28 06:56 UTCVendor advisory
- 2026-07-28 06:56 UTCGHSA enrichment
- 2026-07-28 02:56 UTCVendor advisory
- 2026-07-28 02:56 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-27 22:58 UTCVendor advisory
- 2026-07-27 22:58 UTCGHSA enrichment
- 2026-07-27 19:24 UTCCISA KEV update
- 2026-07-27 18:59 UTCVendor advisory
- 2026-07-27 18:58 UTCGHSA enrichment
- 2026-07-27 17:17 UTCCISA KEV update
- 2026-07-27 14:51 UTCVendor advisory
- 2026-07-27 14:51 UTCGHSA enrichment
- 2026-07-27 10:06 UTCVendor advisory
- 2026-07-27 10:06 UTCGHSA enrichment
- 2026-07-27 06:08 UTCVendor advisory
- 2026-07-27 06:07 UTCGHSA enrichment
- 2026-07-27 02:09 UTCVendor advisory
- 2026-07-27 02:08 UTCGHSA enrichment
- 2026-07-26 22:10 UTCVendor advisory
- 2026-07-26 22:09 UTCGHSA enrichment
- 2026-07-26 18:10 UTCVendor advisory
- 2026-07-26 18:10 UTCGHSA enrichment
- 2026-07-26 14:09 UTCEG score recompute
- 2026-07-26 14:09 UTCVendor advisory
- 2026-07-26 14:09 UTCGHSA enrichment
- 2026-07-26 10:09 UTCVendor advisory
- 2026-07-26 10:09 UTCGHSA enrichment
- 2026-07-26 06:09 UTCVendor advisory
- 2026-07-26 06:09 UTCGHSA enrichment
- 2026-07-26 02:08 UTCEG score recompute
- 2026-07-26 02:08 UTCVendor advisory
- 2026-07-26 02:08 UTCGHSA enrichment
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 02:01 UTCEG score recompute
- 2026-07-22 23:57 UTCEG score recompute
- 2026-07-22 23:57 UTCVendor advisory
- 2026-07-22 23:57 UTCGHSA enrichment
- 2026-07-22 22:48 UTCEG score recompute
- 2026-07-22 19:57 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 15:58 UTCEG score recompute
- 2026-07-22 15:58 UTCVendor advisory
- 2026-07-22 15:57 UTCGHSA enrichment
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 11:58 UTCVendor advisory
- 2026-07-22 11:58 UTCGHSA enrichment
- 2026-07-22 07:59 UTCVendor advisory
- 2026-07-22 07:59 UTCGHSA enrichment
- 2026-07-22 04:01 UTCVendor advisory
- 2026-07-22 04:01 UTCGHSA enrichment
- 2026-07-22 00:01 UTCVendor advisory
- 2026-07-22 00:01 UTCGHSA enrichment
- 2026-07-21 20:02 UTCVendor advisory
- 2026-07-21 20:02 UTCGHSA enrichment
- 2026-07-21 16:03 UTCVendor advisory
- 2026-07-21 16:03 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 12:04 UTCVendor advisory
- 2026-07-21 12:04 UTCGHSA enrichment
- 2026-07-21 08:06 UTCVendor advisory
- 2026-07-21 08:06 UTCGHSA enrichment
- 2026-07-21 04:08 UTCVendor advisory
- 2026-07-21 04:07 UTCGHSA enrichment
- 2026-07-21 00:08 UTCVendor advisory
- 2026-07-21 00:08 UTCGHSA enrichment
- 2026-07-20 20:09 UTCVendor advisory
- 2026-07-20 20:09 UTCGHSA enrichment
- 2026-07-20 16:10 UTCGHSA enrichment
- 2026-07-20 12:11 UTCGHSA enrichment
- 2026-07-20 08:12 UTCVendor advisory
- 2026-07-20 08:11 UTCGHSA enrichment
- 2026-07-20 04:13 UTCVendor advisory
- 2026-07-20 04:13 UTCGHSA enrichment
- 2026-07-20 00:14 UTCVendor advisory
- 2026-07-19 20:15 UTCVendor advisory
- 2026-07-19 20:15 UTCGHSA enrichment
- 2026-07-19 16:15 UTCVendor advisory
Publicly available exploits
(3 references)Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCdemossl/CVE-2021-33766-ProxyTokenFirst seen Sep 15, 2021
CVE-2021-33766-poc
Open source ↗ - GitHub PoCbhdresh/CVE-2021-33766First seen Aug 31, 2021
ProxyToken (CVE-2021-33766) : An Authentication Bypass in Microsoft Exchange Server POC exploit
Open source ↗ - Nucleihttp/cves/2021/CVE-2021-33766.yamlFirst seen Jan 1, 2021
Microsoft Exchange - Authentication Bypass
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-287
Frequently asked(6)
What is CVE-2021-33766?
When was CVE-2021-33766 disclosed?
Is CVE-2021-33766 actively exploited?
What is the CVSS score of CVE-2021-33766?
Which products are affected by CVE-2021-33766?
How do I remediate CVE-2021-33766?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2021-33766
Is Your Infrastructure Affected by CVE-2021-33766?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.