CVE-2017-0191

MEDIUMNVD 5.85.8—
EchelonGraph scoreMEDIUM confidence

Score 5.8 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 5.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 5%CVSS: 5.8Exploit: NoneExposed: 0

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

A denial of service vulnerability exists in the way that Windows 7, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 handles objects in memory. An attacker who successfully exploited the vulnerability could cause a target system to stop responding, aka "Windows Denial of Service Vulnerability."

CVSS v3
5.8
EG Score
5.8(medium)
EPSS
90.8%
KEV
Not listed

Published

April 12, 2017

Last Modified

May 13, 2026

References (6)

Data Freshness Timeline

(refreshed 10× in last 7d / 35× 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-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 02:20 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-05 02:27 UTCEPSS rescore
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-29 14:03 UTCEPSS rescore
  12. 2026-06-28 14:04 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-27 03:05 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-22 14:23 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-21 01:57 UTCEPSS rescore
  21. 2026-06-19 19:23 UTCEPSS rescore
  22. 2026-06-19 19:23 UTCEPSS rescore
  23. 2026-06-18 17:50 UTCEPSS rescore
  24. 2026-06-18 17:50 UTCEPSS rescore
  25. 2026-06-17 17:50 UTCEPSS rescore
Show 43 more
  1. 2026-06-17 17:50 UTCEPSS rescore
  2. 2026-06-16 17:50 UTCEPSS rescore
  3. 2026-06-15 17:45 UTCEPSS rescore
  4. 2026-06-14 23:14 UTCEPSS rescore
  5. 2026-06-14 23:14 UTCEPSS rescore
  6. 2026-06-13 22:57 UTCEPSS rescore
  7. 2026-06-13 22:57 UTCEPSS rescore
  8. 2026-06-12 23:09 UTCEPSS rescore
  9. 2026-06-11 13:57 UTCEPSS rescore
  10. 2026-06-08 14:14 UTCEPSS rescore
  11. 2026-06-06 13:45 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-05 22:44 UTCEPSS rescore
  14. 2026-06-05 06:08 UTCEPSS rescore
  15. 2026-06-05 06:08 UTCEPSS rescore
  16. 2026-06-04 13:10 UTCEPSS rescore
  17. 2026-06-04 13:10 UTCEPSS rescore
  18. 2026-06-02 20:10 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-06-01 13:49 UTCEPSS rescore
  21. 2026-05-31 22:28 UTCEPSS rescore
  22. 2026-05-31 22:28 UTCEPSS rescore
  23. 2026-05-31 00:14 UTCEPSS rescore
  24. 2026-05-29 13:41 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-28 13:42 UTCEPSS rescore
  27. 2026-05-27 13:38 UTCEPSS rescore
  28. 2026-05-27 13:38 UTCEPSS rescore
  29. 2026-05-26 13:42 UTCEPSS rescore
  30. 2026-05-26 13:42 UTCEPSS rescore
  31. 2026-05-26 07:17 UTCEPSS rescore
  32. 2026-05-24 16:44 UTCEPSS rescore
  33. 2026-05-22 21:15 UTCEPSS rescore
  34. 2026-05-22 14:25 UTCEG score recompute
  35. 2026-05-22 14:24 UTCGHSA enrichment
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 22:37 UTCEPSS rescore
  39. 2026-05-20 11:21 UTCEPSS rescore
  40. 2026-05-20 11:21 UTCEPSS rescore
  41. 2026-05-18 21:30 UTCEPSS rescore
  42. 2026-05-18 21:30 UTCEPSS rescore
  43. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-0191?
CVE-2017-0191 is a medium vulnerability published on April 12, 2017. A denial of service vulnerability exists in the way that Windows 7, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 handles objects in memory. An attacker who successfully exploited the vulnerability could cause a target system…
When was CVE-2017-0191 disclosed?
CVE-2017-0191 was first published in the National Vulnerability Database on April 12, 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-0191 actively exploited?
CVE-2017-0191 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-0191?
CVE-2017-0191 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2017-0191?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0191, 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-0191

Explore →

Is Your Infrastructure Affected by CVE-2017-0191?

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

Start Free Scan →Browse All CVEs