CVE-2017-0145

CRITICALNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-02-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 90%CVSS: 8.8Exploit: cisa kev · ssvc active · kev ransomware · Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607; and Windows Server 2016 allows remote attackers to execute arbitrary code via crafted packets, aka "Windows SMB Remote Code Execution Vulnerability." This vulnerability is different from those described in CVE-2017-0143, CVE-2017-0144, CVE-2017-0146, and CVE-2017-0148.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

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
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
90%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 17, 2017

Last Modified

August 14, 2026

Advisory Details (6)

Auto-updated May 2, 2026
🔬 Proof of concept available. Patch available. Sources: microsoft.
generic🟡 PoC Available

Microsoft Windows Server 2008 R2 (x64) - 'SrvOs2FeaToNt' SMB Remote Code Execution (MS17-010) - Windows_x86-64 remote Exploit

https://www.exploit-db.com/exploits/41987/
generic🟡 PoC Available

Microsoft Windows - SMB Remote Code Execution Scanner (MS17-010) (Metasploit) - Windows dos Exploit

https://www.exploit-db.com/exploits/41891/
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-2017-0145

Vendor Advisories for CVE-2017-0145(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 100× in last 7d / 422× 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,724 total refreshes for this CVE.

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

Publicly available exploits

(6 references)

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

  • Exploit-DBEDB-47456✓ verified
    First seen Oct 2, 2019

    DOUBLEPULSAR - Payload Execution and Neutralization (Metasploit)

    Open source ↗
  • Exploit-DBEDB-41891✓ verified
    First seen Apr 17, 2017

    Microsoft Windows - SMB Remote Code Execution Scanner (MS17-010) (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/smb/smb_doublepulsar_rce✓ verified
    First seen Apr 14, 2017

    SMB DOUBLEPULSAR Remote Code Execution

    Open source ↗
  • Metasploitexploit/windows/smb/ms17_010_eternalblue✓ verified
    First seen Mar 14, 2017

    MS17-010 EternalBlue SMB Remote Windows Kernel Pool Corruption

    Open source ↗
  • Metasploitauxiliary/scanner/smb/smb_ms17_010✓ verified
    First seen Jan 1, 2017

    MS17-010 SMB RCE Detection

    Open source ↗
  • Exploit-DBEDB-41987
    First seen May 10, 2017

    Microsoft Windows Server 2008 R2 (x64) - 'SrvOs2FeaToNt' SMB Remote Code Execution (MS17-010)

    Open source ↗

Frequently asked(6)

What is CVE-2017-0145?
CVE-2017-0145 is a critical vulnerability published on March 17, 2017. The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607; and Windows Server 2016 allows remote attackers to execute arbitrary code via crafted packets, aka…
When was CVE-2017-0145 disclosed?
CVE-2017-0145 was first published on March 17, 2017, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-0145 actively exploited?
Yes. CISA added CVE-2017-0145 to the Known Exploited Vulnerabilities catalog on February 10, 2022, affecting Microsoft SMBv1. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2017-0145?
CVE-2017-0145 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2017-0145?
CVE-2017-0145 affects Microsoft SMBv1.
How do I remediate CVE-2017-0145?
A fix for CVE-2017-0145 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-0145 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-0145

Explore →

Is Your Infrastructure Affected by CVE-2017-0145?

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