CVE-2016-0099: Windows Secondary Logon Elevation of Privilege Vulnerability
- Vendor
- Microsoft Corporation
CVE-2016-0099 is a local privilege-escalation vulnerability in the Microsoft Windows Secondary Logon Service caused by improper processing of request handles. A local user can exploit the flaw through a crafted application to gain elevated privileges. Exploit implementations use the CreateProcessWithLogonW API. Affected releases include Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 and 2012 R2; Windows RT 8.1; and Windows 10 initial release and version 1511. The vulnerability is associated with MS16-032.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation elevates the privileges of a local user, allowing attacker-controlled activity to run with greater authority on the affected Windows system. The vulnerability has been used in post-compromise operations involving Earth Akhlut, Prometei, and Makop, and is included in offensive tooling such as PoshC2. The available details do not establish the precise resulting privilege level or specific confidentiality and availability consequences.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce opportunities for local code execution by limiting interactive logon rights, restricting execution of untrusted binaries and scripts through application control, and minimizing the number of users with local access to affected systems. Monitor for suspicious use of Secondary Logon-related behavior and anomalous privilege-escalation activity from low-privileged contexts. Hardening measures that reduce post-compromise execution paths can lower exploitability, but they do not remove the underlying flaw.
Remediation
Patch, then assume compromise.
Apply the Microsoft security update addressing CVE-2016-0099 under MS16-032, or a superseding update appropriate for the affected Windows release.
Exploits
2 exploits validated by Mallory's analysis. Hidden: 3 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2016-0099 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 3, 2022.
- Is there a public exploit for CVE-2016-0099?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2016-0099, the earliest disclosed Mar 21, 2016.
- Is there a patch for CVE-2016-0099?
- Apply the Microsoft security update addressing CVE-2016-0099 under MS16-032, or a superseding update appropriate for the affected Windows release.
- What products are affected by CVE-2016-0099?
- Microsoft Corporation Windows 7, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Server 2008, Microsoft Corporation Windows Server 2012, Microsoft Corporation Windows Vista, and 2 more.
- How severe is CVE-2016-0099?
- CVE-2016-0099 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 37.0% (99th percentile) as of Oct 16, 2026.
Recent activity
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.