CVE-2020-17132

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.1
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
CISA-KEV: Not listedEPSS: 90%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Microsoft Exchange Remote Code Execution Vulnerability

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
81(Track*)
EG Risk 81/100SSVC: Track*

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 computed
Severity91% × 45%
Exploitation90% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.8%
KEV
Not listed

Published

December 10, 2020

Last Modified

August 28, 2025

Advisory Details (2)

Auto-updated Jul 22, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

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-2020-17132
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-17132

Weakness 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 4× in last 7d / 7× 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.

  1. 2026-07-24 14:14 UTCEPSS rescore
  2. 2026-07-23 01:50 UTCEG score recompute
  3. 2026-07-22 22:35 UTCEG score recompute
  4. 2026-07-22 14:05 UTCEPSS rescore
  5. 2026-07-09 19:07 UTCEPSS rescore
  6. 2026-07-01 15:03 UTCEPSS rescore
  7. 2026-06-25 13:47 UTCEPSS rescore
  8. 2026-06-23 21:31 UTCEPSS rescore
  9. 2026-06-23 21:31 UTCEPSS rescore
  10. 2026-06-22 14:23 UTCEPSS rescore
  11. 2026-06-22 14:23 UTCEPSS rescore
  12. 2026-06-17 17:50 UTCEPSS rescore
  13. 2026-06-15 17:46 UTCEPSS rescore
  14. 2026-06-13 22:58 UTCEPSS rescore
  15. 2026-06-13 22:58 UTCEPSS rescore
  16. 2026-06-12 23:10 UTCEPSS rescore
  17. 2026-06-10 22:16 UTCEPSS rescore
  18. 2026-06-10 22:16 UTCEPSS rescore
  19. 2026-06-10 13:20 UTCEPSS rescore
  20. 2026-06-08 14:15 UTCEPSS rescore
  21. 2026-06-08 14:15 UTCEPSS rescore
  22. 2026-06-07 15:23 UTCEPSS rescore
  23. 2026-06-07 15:23 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
Show 18 more
  1. 2026-06-05 22:45 UTCEPSS rescore
  2. 2026-06-05 22:45 UTCEPSS rescore
  3. 2026-06-05 06:08 UTCEPSS rescore
  4. 2026-06-05 06:08 UTCEPSS rescore
  5. 2026-06-04 13:10 UTCEPSS rescore
  6. 2026-06-04 13:10 UTCEPSS rescore
  7. 2026-06-01 13:50 UTCEPSS rescore
  8. 2026-06-01 13:50 UTCEPSS rescore
  9. 2026-05-31 22:29 UTCEPSS rescore
  10. 2026-05-31 22:29 UTCEPSS rescore
  11. 2026-05-31 00:15 UTCEPSS rescore
  12. 2026-05-31 00:15 UTCEPSS rescore
  13. 2026-05-28 13:43 UTCEPSS rescore
  14. 2026-05-28 13:43 UTCEPSS rescore
  15. 2026-05-27 13:39 UTCEPSS rescore
  16. 2026-05-23 04:27 UTCEG score recompute
  17. 2026-05-23 04:27 UTCVendor advisory
  18. 2026-05-23 04:27 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_ecp_dlp_policy✓ verified
    First seen Jan 12, 2021

    Microsoft Exchange Server DlpUtils AddTenantDlpPolicy RCE

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2020-17132?
CVE-2020-17132 is a critical vulnerability published on December 10, 2020. Microsoft Exchange Remote Code Execution Vulnerability
When was CVE-2020-17132 disclosed?
CVE-2020-17132 was first published in the National Vulnerability Database on December 10, 2020, with the most recent update on August 28, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-17132 actively exploited?
CVE-2020-17132 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-17132?
CVE-2020-17132 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2020-17132?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-17132, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-17132

Explore →

Is Your Infrastructure Affected by CVE-2020-17132?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs