CVE-2017-0148

CRITICALNVD 8.19.0▲
EchelonGraph scoreHIGH confidence

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

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 4 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: 99%CVSS: 8.1Exploit: 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-0145, and CVE-2017-0146.

CVSS v3
8.1
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
99%
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

June 17, 2026

Advisory Details (7)

Auto-updated May 19, 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-0148

Vendor Advisories for CVE-2017-0148(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 91× in last 7d / 382× 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,602 total refreshes for this CVE.

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

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-0148?
CVE-2017-0148 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-0148 disclosed?
CVE-2017-0148 was first published on March 17, 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-0148 actively exploited?
Yes. CISA added CVE-2017-0148 to the Known Exploited Vulnerabilities catalog on April 6, 2022, affecting Microsoft SMBv1 server. 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-0148?
CVE-2017-0148 has a CVSS v3 base score of 8.1 (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-0148?
CVE-2017-0148 affects Microsoft SMBv1 server.
How do I remediate CVE-2017-0148?
A fix for CVE-2017-0148 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-0148 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-0148?

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