CVE-2017-0290

HIGHNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 88% probability of exploitation within the next 30 days (top 0.5% 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
7.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 77%
CISA-KEV: Not listedEPSS: 77%CVSS: 7.8Exploit: NoneExposed: 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 does not properly scan a specially crafted file leading to memory corruption, aka "Microsoft Malware Protection Engine Remote Code Execution Vulnerability."

CVSS v3
7.8
EG Score
9.0(high)
EPSS
99.5%
KEV
Not listed

Published

May 9, 2017

Last Modified

May 13, 2026

References (20)

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 6× in last 7d / 25× 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-06 16:24 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-04 06:28 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-30 23:19 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-28 14:04 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-27 03:05 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-24 14:02 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-22 14:23 UTCEPSS rescore
  14. 2026-06-21 14:54 UTCEPSS rescore
  15. 2026-06-21 14:54 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-21 01:57 UTCEPSS rescore
  18. 2026-06-17 17:50 UTCEPSS rescore
  19. 2026-06-17 17:50 UTCEPSS rescore
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-14 23:14 UTCEPSS rescore
  22. 2026-06-14 23:14 UTCEPSS rescore
  23. 2026-06-13 22:57 UTCEPSS rescore
  24. 2026-06-13 22:57 UTCEPSS rescore
  25. 2026-06-12 23:09 UTCEPSS rescore
Show 23 more
  1. 2026-06-06 13:45 UTCEPSS rescore
  2. 2026-06-06 13:45 UTCEPSS rescore
  3. 2026-06-01 13:49 UTCEPSS rescore
  4. 2026-06-01 13:49 UTCEPSS rescore
  5. 2026-05-31 22:28 UTCEPSS rescore
  6. 2026-05-31 22:28 UTCEPSS rescore
  7. 2026-05-29 13:41 UTCEPSS rescore
  8. 2026-05-28 13:42 UTCEPSS rescore
  9. 2026-05-28 13:42 UTCEPSS rescore
  10. 2026-05-27 13:38 UTCEPSS rescore
  11. 2026-05-27 13:38 UTCEPSS rescore
  12. 2026-05-26 07:17 UTCEPSS rescore
  13. 2026-05-22 21:15 UTCEPSS rescore
  14. 2026-05-22 13:34 UTCEG score recompute
  15. 2026-05-22 13:34 UTCVendor advisory
  16. 2026-05-22 13:33 UTCGHSA enrichment
  17. 2026-05-20 22:37 UTCEPSS rescore
  18. 2026-05-20 22:37 UTCEPSS rescore
  19. 2026-05-20 22:37 UTCEPSS rescore
  20. 2026-05-19 13:33 UTCOSV refresh
  21. 2026-05-18 21:30 UTCEPSS rescore
  22. 2026-05-18 21:30 UTCEPSS rescore
  23. 2026-05-18 21:30 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-41975✓ verified
    First seen May 9, 2017

    Microsoft Security Essentials / SCEP (Microsoft Windows 8/8.1/10 / Windows Server) - 'MsMpEng' Remote Type Confusion

    Open source ↗

Frequently asked(5)

What is CVE-2017-0290?
CVE-2017-0290 is a high vulnerability published on May 9, 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 does not…
When was CVE-2017-0290 disclosed?
CVE-2017-0290 was first published in the National Vulnerability Database on May 9, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-0290 actively exploited?
CVE-2017-0290 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-0290?
CVE-2017-0290 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2017-0290?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0290, 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-0290

Explore →

Is Your Infrastructure Affected by CVE-2017-0290?

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

Start Free Scan →Browse All CVEs