Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2016-0099: Windows Secondary Logon Elevation of Privilege Vulnerability

Published Mar 9, 2016 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS37.0%99th percentile
CISA KEVYesAdded Mar 3, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2016-0099CWE-269

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 3 not yet analyzed, such as Exploit-DB entries.

View more in app →
ms16_032_secondary_logon_handle_privesc.rbThis repository contains a single Metasploit module implementing a local privilege escalation exploit for Microsoft Windows (CVE-2016-0099, MS16-032). The exploit targets a vulnerability in the Secondary Logon Service, allowing an attacker with a Meterpreter session on a vulnerable Windows system (Windows 7, 8, 10, 2008, 2012) to escalate privileges to SYSTEM. The module checks for the required number of CPU cores and PowerShell version, writes a PowerShell payload to a temporary file, and executes it with SYSTEM privileges using a crafted script. The payload is customizable and typically provides a Meterpreter shell. The exploit is weaponized, part of the Metasploit framework, and leverages local file paths and PowerShell for payload delivery and execution.Disclosed Mar 21, 2016 · Framework: metasploit · ruby · localWeaponizedMS16-032This repository contains a Visual Studio project for an exploit targeting MS16-032 (CVE-2016-0099), a Windows privilege escalation vulnerability. The structure includes a solution file, project files, and references to a main C++ source file (ms16-032.cpp), which is not included in the provided content. The README specifies that the exploit is intended for use in a service context, indicating it must be run as a Windows service to function. The project is configured for both 32-bit and 64-bit Windows builds. No network endpoints or external IPs are present; the attack vector is local privilege escalation. The repository is a proof-of-concept (POC) for local exploitation and does not appear to be weaponized or part of a larger framework. The main fingerprintable endpoint is the source file path for the exploit code.zcgonvh · Disclosed Mar 15, 2017 · cpp · xml · localPoC
Exposure surface

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.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1511operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Vistaoperating_system
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware8Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.