Windows Hyper-V allows an elevation of privilege vulnerability when Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 201…

published 2017-05-12 9y ago modified 2026-06-17 4mo ago also EUVD-2017-0578

cvss: 7.6; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits: 0; none known

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".

Patch / fix

links 1

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0212 advisory

Is CVE-2017-0212 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.6	CVSS:3.0/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
NVD	2.0	5.4	AV:A/AC:M/Au:N/C:P/I:P/A:P

Affected products

Microsoft Corporation Microsoft Hyper-V

Classification

Weakness

CWE-20 Improper Input Validation

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2017-0212
patch, vendor-advisory
securityfocus.com /bid/98099
vdb-entry, third-party-advisory

Sources

CVE List CVE-2017-0212
NVD CVE-2017-0212

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.