CVE-2017-8538

HIGHNVD 7.88.2▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.2 because EPSS predicts 50% probability of exploitation within the next 30 days (top 1.2% of all CVEs). NVD baseline CVSS 7.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
8.2EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 50%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 50%CVSS: 7.8Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

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

The Microsoft Malware Protection Engine running on Microsoft Forefront and Microsoft Defender on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016, Microsoft Exchange Server 2013 and 2016, does not properly scan a specially crafted file leading to memory corruption. aka "Microsoft Malware Protection Engine Remote Code Execution Vulnerability", a different vulnerability than CVE-2017-8540 and CVE-2017-8541.

CVSS v3
7.8
EG Score
8.2(high)
EG Risk
67(Track)
EG Risk 67/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
Severity82% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
50%
EPSS %ILE
99%
KEV
Not listed

Published

May 26, 2017

Last Modified

June 17, 2026

References (8)

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 / 15× 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 121 total refreshes for this CVE.

  1. 2026-09-24 13:59 UTCEPSS rescore
  2. 2026-09-23 13:42 UTCEPSS rescore
  3. 2026-09-21 20:27 UTCEPSS rescore
  4. 2026-09-19 15:36 UTCEPSS rescore
  5. 2026-09-17 19:22 UTCEPSS rescore
  6. 2026-09-17 19:22 UTCEPSS rescore
  7. 2026-09-15 03:05 UTCEPSS rescore
  8. 2026-09-12 14:56 UTCEPSS rescore
  9. 2026-09-05 15:24 UTCEPSS rescore
  10. 2026-09-04 13:56 UTCEPSS rescore
  11. 2026-09-02 14:07 UTCEPSS rescore
  12. 2026-09-02 14:07 UTCEPSS rescore
  13. 2026-09-01 03:31 UTCEPSS rescore
  14. 2026-08-30 19:13 UTCEPSS rescore
  15. 2026-08-28 21:36 UTCEPSS rescore
  16. 2026-08-26 14:41 UTCEPSS rescore
  17. 2026-08-25 13:44 UTCEPSS rescore
  18. 2026-08-21 23:44 UTCEPSS rescore
  19. 2026-08-19 16:59 UTCEPSS rescore
  20. 2026-08-18 13:43 UTCEPSS rescore
  21. 2026-08-16 14:51 UTCEPSS rescore
  22. 2026-08-16 02:10 UTCEPSS rescore
  23. 2026-08-15 01:26 UTCEPSS rescore
  24. 2026-08-12 13:46 UTCEPSS rescore
  25. 2026-08-07 16:22 UTCEPSS rescore
Show 75 more
  1. 2026-08-06 13:42 UTCEPSS rescore
  2. 2026-08-06 13:42 UTCEPSS rescore
  3. 2026-08-02 02:23 UTCEPSS rescore
  4. 2026-08-02 02:23 UTCEPSS rescore
  5. 2026-07-30 16:24 UTCEPSS rescore
  6. 2026-07-30 01:26 UTCEPSS rescore
  7. 2026-07-28 15:32 UTCEPSS rescore
  8. 2026-07-26 14:51 UTCEPSS rescore
  9. 2026-07-26 14:51 UTCEPSS rescore
  10. 2026-07-23 14:15 UTCEPSS rescore
  11. 2026-07-23 01:30 UTCEG score recompute▲ 0.40
  12. 2026-07-22 22:10 UTCEG score recompute
  13. 2026-07-22 14:04 UTCEPSS rescore
  14. 2026-07-21 15:21 UTCEPSS rescore
  15. 2026-07-20 17:04 UTCEPSS rescore
  16. 2026-07-20 17:04 UTCEPSS rescore
  17. 2026-07-19 02:26 UTCEPSS rescore
  18. 2026-07-19 02:26 UTCEPSS rescore
  19. 2026-07-16 16:59 UTCEPSS rescore
  20. 2026-07-16 16:59 UTCEPSS rescore
  21. 2026-07-15 16:55 UTCEPSS rescore
  22. 2026-07-15 16:54 UTCEPSS rescore
  23. 2026-07-13 22:26 UTCEPSS rescore
  24. 2026-07-13 22:26 UTCEPSS rescore
  25. 2026-07-11 08:24 UTCEPSS rescore
  26. 2026-07-09 19:06 UTCEPSS rescore
  27. 2026-07-08 15:11 UTCEPSS rescore
  28. 2026-07-06 16:24 UTCEPSS rescore
  29. 2026-07-06 16:24 UTCEPSS rescore
  30. 2026-07-06 02:20 UTCEPSS rescore
  31. 2026-07-06 02:20 UTCEPSS rescore
  32. 2026-07-05 02:27 UTCEPSS rescore
  33. 2026-07-02 16:54 UTCEPSS rescore
  34. 2026-07-01 15:03 UTCEPSS rescore
  35. 2026-06-28 04:53 UTCEPSS rescore
  36. 2026-06-28 04:53 UTCEPSS rescore
  37. 2026-06-27 03:06 UTCEPSS rescore
  38. 2026-06-25 13:47 UTCEPSS rescore
  39. 2026-06-24 14:02 UTCEPSS rescore
  40. 2026-06-24 14:02 UTCEPSS rescore
  41. 2026-06-23 21:30 UTCEPSS rescore
  42. 2026-06-23 21:30 UTCEPSS rescore
  43. 2026-06-22 14:23 UTCEPSS rescore
  44. 2026-06-22 14:23 UTCEPSS rescore
  45. 2026-06-21 01:57 UTCEPSS rescore
  46. 2026-06-21 01:57 UTCEPSS rescore
  47. 2026-06-18 17:50 UTCEPSS rescore
  48. 2026-06-17 17:50 UTCEPSS rescore
  49. 2026-06-16 17:50 UTCEPSS rescore
  50. 2026-06-15 17:45 UTCEPSS rescore
  51. 2026-06-14 23:14 UTCEPSS rescore
  52. 2026-06-14 23:14 UTCEPSS rescore
  53. 2026-06-13 22:58 UTCEPSS rescore
  54. 2026-06-13 22:57 UTCEPSS rescore
  55. 2026-06-12 23:09 UTCEPSS rescore
  56. 2026-06-12 23:09 UTCEPSS rescore
  57. 2026-06-11 13:57 UTCEPSS rescore
  58. 2026-06-10 22:15 UTCEPSS rescore
  59. 2026-06-10 13:19 UTCEPSS rescore
  60. 2026-06-06 13:45 UTCEPSS rescore
  61. 2026-06-06 13:45 UTCEPSS rescore
  62. 2026-06-05 22:44 UTCEPSS rescore
  63. 2026-06-05 22:44 UTCEPSS rescore
  64. 2026-06-05 06:08 UTCEPSS rescore
  65. 2026-06-05 06:08 UTCEPSS rescore
  66. 2026-06-02 20:11 UTCEPSS rescore
  67. 2026-06-02 20:11 UTCEPSS rescore
  68. 2026-06-01 13:49 UTCEPSS rescore
  69. 2026-06-01 13:49 UTCEPSS rescore
  70. 2026-05-29 13:41 UTCEPSS rescore
  71. 2026-05-26 13:42 UTCEPSS rescore
  72. 2026-05-26 07:17 UTCEPSS rescore
  73. 2026-05-26 07:17 UTCEPSS rescore
  74. 2026-05-22 21:15 UTCEPSS rescore
  75. 2026-05-22 21:15 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-42081✓ verified
    First seen May 29, 2017

    Microsoft MsMpEng - Multiple Crashes While Scanning Malformed Files

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-8538?
CVE-2017-8538 is a high vulnerability published on May 26, 2017. The Microsoft Malware Protection Engine running on Microsoft Forefront and Microsoft Defender on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016, Microsoft…
When was CVE-2017-8538 disclosed?
CVE-2017-8538 was first published in the National Vulnerability Database on May 26, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-8538 actively exploited?
CVE-2017-8538 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50% probability of exploitation in the next 30 days, which ranks it in the top 1.1% of all scored CVEs.
What is the CVSS score of CVE-2017-8538?
CVE-2017-8538 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.2.
How do I remediate CVE-2017-8538?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-8538, 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-2017-8538

Explore →

Is Your Infrastructure Affected by CVE-2017-8538?

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

Book a Demo →Browse All CVEs