CVE-2016-0181

CVE-2016-0181 is a medium-severity vulnerability in Microsoft Windows 10 with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-254.

Key facts

Description

Microsoft Windows 10 Gold and 1511 allows local users to bypass the Virtual Secure Mode Hypervisor Code Integrity (HVCI) protection mechanism and perform RWX markings of kernel-mode pages via a crafted application, aka "Hypervisor Code Integrity Security Feature Bypass."

Frequently asked questions

What is CVE-2016-0181?
Microsoft Windows 10 Gold and 1511 allows local users to bypass the Virtual Secure Mode Hypervisor Code Integrity (HVCI) protection mechanism and perform RWX markings of kernel-mode pages via a crafted application, aka "Hypervisor Code Integrity Security Feature Bypass."
How severe is CVE-2016-0181?
CVE-2016-0181 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2016-0181 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (71st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-0181?
CVE-2016-0181 primarily affects Microsoft Windows 10. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-0181?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2016-0181 published?
CVE-2016-0181 was published on 2016-05-11 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Microsoft Windows 10

All CVEs affecting Microsoft Windows 10 →

Other CWE-254 vulnerabilities

Browse all CWE-254 vulnerabilities →