Windows Hyper-V allows an elevation of privilege vulnerability when Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 fail to properly validate vSMB packet data, aka "Windows Hyper-V vSMB Elevation of Privilege Vulnerability".
CVE-2017-0212
HIGHNVD 7.67.6—
EchelonGraph scoreMEDIUM confidence
Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.6; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.6Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.6
- EG Score
- 7.6(medium)
- EPSS
- 62.7%
- KEV
- Not listed
Published
May 12, 2017
Last Modified
May 13, 2026
References (4)
- secure@microsofthttp://www.securityfocus.com/bid/98099
- secure@microsofthttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0212
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/98099
- af854a3a-2127-422b-91ae-364da2661108https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0212
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.
Frequently asked(5)
What is CVE-2017-0212?
CVE-2017-0212 is a high vulnerability published on May 12, 2017. Windows Hyper-V allows an elevation of privilege vulnerability when Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 fail to properly validate vSMB packet data, aka "Windows Hyper-V vSMB Elevation of Privilege Vulnerability".
When was CVE-2017-0212 disclosed?
CVE-2017-0212 was first published in the National Vulnerability Database on May 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-0212 actively exploited?
CVE-2017-0212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 62.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-0212?
CVE-2017-0212 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2017-0212?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0212, 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-0212
Is Your Infrastructure Affected by CVE-2017-0212?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.