An elevation of privilege vulnerability exists in Microsoft Exchange Server, aka "Microsoft Exchange Server Elevation of Privilege Vulnerability." This affects Microsoft Exchange Server.
CVE-2018-8581
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.4 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.4
- 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
- 27%
- EPSS %ILE
- 98%
- KEV
- ⚠ Exploited
Published
November 14, 2018
Last Modified
October 28, 2025
Advisory Details (4)
Auto-updated Jun 6, 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-2018-8581Security 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-2018-8581All 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 98× in last 7d / 362× 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,073 total refreshes for this CVE.
- 2026-08-21 17:44 UTCGHSA enrichment
- 2026-08-21 16:49 UTCCISA KEV update
- 2026-08-21 13:48 UTCVendor advisory
- 2026-08-21 13:48 UTCGHSA enrichment
- 2026-08-21 09:51 UTCVendor advisory
- 2026-08-21 09:51 UTCGHSA enrichment
- 2026-08-21 05:55 UTCVendor advisory
- 2026-08-21 05:55 UTCGHSA enrichment
- 2026-08-21 01:59 UTCEG score recompute
- 2026-08-21 01:59 UTCVendor advisory
- 2026-08-21 01:59 UTCGHSA enrichment
- 2026-08-20 22:51 UTCEPSS rescore
- 2026-08-20 22:03 UTCVendor advisory
- 2026-08-20 22:03 UTCGHSA enrichment
- 2026-08-20 18:07 UTCVendor advisory
- 2026-08-20 18:07 UTCGHSA enrichment
- 2026-08-20 17:06 UTCCISA KEV update
- 2026-08-20 14:11 UTCVendor advisory
- 2026-08-20 14:11 UTCGHSA enrichment
- 2026-08-20 10:15 UTCVendor advisory
- 2026-08-20 10:15 UTCGHSA enrichment
- 2026-08-20 06:20 UTCGHSA enrichment
- 2026-08-20 02:24 UTCGHSA enrichment
- 2026-08-19 22:28 UTCVendor advisory
- 2026-08-19 22:28 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-19 18:32 UTCEG score recompute
- 2026-08-19 18:32 UTCVendor advisory
- 2026-08-19 18:31 UTCGHSA enrichment
- 2026-08-19 17:33 UTCCISA KEV update
- 2026-08-19 17:00 UTCEPSS rescore
- 2026-08-19 14:35 UTCVendor advisory
- 2026-08-19 14:35 UTCGHSA enrichment
- 2026-08-19 10:39 UTCVendor advisory
- 2026-08-19 10:39 UTCGHSA enrichment
- 2026-08-19 06:42 UTCVendor advisory
- 2026-08-19 06:42 UTCGHSA enrichment
- 2026-08-19 02:45 UTCVendor advisory
- 2026-08-19 02:44 UTCGHSA enrichment
- 2026-08-18 22:46 UTCGHSA enrichment
- 2026-08-18 18:51 UTCVendor advisory
- 2026-08-18 18:51 UTCGHSA enrichment
- 2026-08-18 16:58 UTCCISA KEV update
- 2026-08-18 14:54 UTCEG score recompute
- 2026-08-18 14:54 UTCVendor advisory
- 2026-08-18 14:54 UTCGHSA enrichment
- 2026-08-18 13:44 UTCEPSS rescore
- 2026-08-18 10:59 UTCVendor advisory
- 2026-08-18 10:59 UTCGHSA enrichment
- 2026-08-18 07:02 UTCGHSA enrichment
- 2026-08-18 03:06 UTCVendor advisory
- 2026-08-18 03:05 UTCGHSA enrichment
- 2026-08-17 23:09 UTCVendor advisory
- 2026-08-17 23:08 UTCGHSA enrichment
- 2026-08-17 19:11 UTCVendor advisory
- 2026-08-17 19:11 UTCGHSA enrichment
- 2026-08-17 15:14 UTCVendor advisory
- 2026-08-17 15:14 UTCGHSA enrichment
- 2026-08-17 13:56 UTCCISA KEV update
- 2026-08-17 11:18 UTCVendor advisory
- 2026-08-17 11:18 UTCGHSA enrichment
- 2026-08-17 07:22 UTCVendor advisory
- 2026-08-17 07:22 UTCGHSA enrichment
- 2026-08-17 03:27 UTCVendor advisory
- 2026-08-17 03:27 UTCGHSA enrichment
- 2026-08-16 23:31 UTCVendor advisory
- 2026-08-16 23:31 UTCGHSA enrichment
- 2026-08-16 19:35 UTCVendor advisory
- 2026-08-16 19:35 UTCGHSA enrichment
- 2026-08-16 15:39 UTCEG score recompute
- 2026-08-16 15:39 UTCVendor advisory
- 2026-08-16 15:39 UTCGHSA enrichment
- 2026-08-16 14:52 UTCEPSS rescore
- 2026-08-16 11:43 UTCVendor advisory
- 2026-08-16 11:43 UTCGHSA enrichment
- 2026-08-16 07:47 UTCVendor advisory
- 2026-08-16 07:47 UTCGHSA enrichment
- 2026-08-16 03:52 UTCEG score recompute
- 2026-08-16 03:52 UTCVendor advisory
- 2026-08-16 03:52 UTCGHSA enrichment
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-15 23:56 UTCVendor advisory
- 2026-08-15 23:56 UTCGHSA enrichment
- 2026-08-15 20:00 UTCVendor advisory
- 2026-08-15 20:00 UTCGHSA enrichment
- 2026-08-15 16:04 UTCVendor advisory
- 2026-08-15 16:04 UTCGHSA enrichment
- 2026-08-15 12:08 UTCVendor advisory
- 2026-08-15 12:08 UTCGHSA enrichment
- 2026-08-15 08:12 UTCVendor advisory
- 2026-08-15 08:12 UTCGHSA enrichment
- 2026-08-15 04:16 UTCEG score recompute
- 2026-08-15 04:16 UTCVendor advisory
- 2026-08-15 04:16 UTCGHSA enrichment
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-15 00:20 UTCVendor advisory
- 2026-08-15 00:20 UTCGHSA enrichment
- 2026-08-14 20:25 UTCVendor advisory
- 2026-08-14 20:25 UTCGHSA enrichment
- 2026-08-14 16:29 UTCVendor advisory
- 2026-08-14 16:29 UTCGHSA enrichment
Publicly available exploits
(3 references)Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCRidter/Exchange2domainFirst seen Jan 24, 2019
CVE-2018-8581
Open source ↗ - GitHub PoCqiantu88/CVE-2018-8581First seen Dec 28, 2018
CVE-2018-8581
Open source ↗ - GitHub PoCWyAtu/CVE-2018-8581First seen Dec 27, 2018
CVE-2018-8581 | Microsoft Exchange Server Elevation of Privilege Vulnerability
Open source ↗
Frequently asked(6)
What is CVE-2018-8581?
When was CVE-2018-8581 disclosed?
Is CVE-2018-8581 actively exploited?
What is the CVSS score of CVE-2018-8581?
Which products are affected by CVE-2018-8581?
How do I remediate CVE-2018-8581?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2018-8581
Is Your Infrastructure Affected by CVE-2018-8581?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.