Threat Reports

SignDrop: Windows CLFS Zero-Day Enables Local Privilege Escalation to SYSTEM

Threat Reports

Published on

Read time

5 min

Share this insight

Summary:

A Windows zero-day named SignDrop, published publicly on GitHub on November 10, 2026 by a researcher operating as MSNightmare, allows a standard local user to escalate privileges to NT AUTHORITY\SYSTEM by abusing the Common Log File System (CLFS) authentication mechanism that Microsoft added to harden the driver. The exploit is a logic chain with no memory corruption that abuses legitimate Windows components, including a Microsoft Defender update interface, to make the CLFS driver create a file as SYSTEM in an attacker-chosen location. No CVE has been assigned, no patch is available, and Microsoft had not commented publicly as of November 11, 2026. Cyderes Howler Cell reproduced a SYSTEM shell, and no in-the-wild exploitation has been confirmed.

Technical Description:

SignDrop targets the CLFS authentication mechanism in clfs.sys, which Microsoft added to sign CLFS log files with HMAC-based authentication codes so that tampered logs fail validation. The mechanism was designed to close the class of logic bugs caused by improper validation of CLFS data structures, which accounted for 19 of 24 CLFS CVEs over five years. SignDrop leaves the signed logs intact and abuses the signing operation itself: it causes clfs.sys to create the signature file as SYSTEM at an attacker-selected path, producing a privileged file creation primitive.

The exploit then converts that primitive into code execution. Because the created file retains attacker-accessible security attributes, the attacker replaces its content with a payload DLL placed in a trusted system directory, where a privileged Windows process loads it, and the payload starts a SYSTEM-level console on the user's desktop while closing the UAC prompt. Microsoft Defender is used unwittingly: the exploit calls Defender's signature update RPC interface to trigger the CLFS operation under SYSTEM context. The chain relies entirely on native Windows behavior and involves no memory corruption.

The flaw affects systems where the registry key HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication exists with Mode set to 0 (enforcement) or 1 (learning), which indicates that CLFS authentication is active. The researcher tested Windows 11 26H2 and experimental builds of Windows 11 and Windows Server 2025 and claims about 80% of Windows installations are vulnerable, but Cyderes notes that no data supports that figure. Disabling CLFS authentication is not a safe workaround because it re-exposes systems to the memory corruption bugs the mitigation was built to stop. No CVE or patch exists.

| CVE | CVSS | Vulnerability Type | Affected Product | Patch Version |

| Not assigned | NA | Local Privilege Escalation (CLFS Authentication Abuse) | Windows CLFS (clfs.sys) | None available |

Exploitation Demonstration:

  • An attacker who already has a foothold on a Windows system as a standard user runs the publicly available exploit; no administrative privileges are required.
  • The exploit prepares a staging location and Object Manager redirections so that CLFS and Microsoft Defender operate on attacker-controlled paths.
  • The exploit triggers Defender's signature update interface, which causes the CLFS driver to create its signature file as SYSTEM in a trusted Windows directory chosen by the attacker.
  • The attacker replaces the file's content with a payload DLL, which a privileged Windows process loads when a UAC elevation request is made.
  • The payload opens a SYSTEM-level console on the user's desktop and closes the UAC prompt, and the exploit deletes the planted DLL to remove evidence.

Ease of Exploitation:

Exploitation requires an attacker to already have local access as a standard user, which limits the initial attack surface, but once that foothold exists, the public proof of concept is effective: Cyderes reproduced every stage and obtained a SYSTEM shell. Because the exploit is a logic chain without memory corruption, it does not depend on memory layout. No patch exists and the exploit code is public, so the risk to affected systems is immediate. No in-the-wild exploitation had been confirmed as of November 10, 2026, but the same researcher has published sixteen zero-day releases since April 2026, often on Patch Tuesday, so follow-up releases are possible.

Conclusion:

SignDrop turns a Windows kernel security mitigation into a privilege escalation path and represents a significant risk to organizations because a working public exploit exists, no patch or CVE is available, and the mitigation cannot safely be disabled. Organizations should prioritize behavioral detection, restrict untrusted local code execution, and monitor for Microsoft's fix.

Impact:

Successful exploitation allows a local attacker with standard user rights to gain NT AUTHORITY\SYSTEM privileges, giving full control of the affected Windows system, including the ability to disable security tools, access sensitive data and credentials, and move laterally. Because the flaw can be chained with any initial foothold, it can turn a limited compromise into full system compromise.

IOC and Context Details:

| Topics | Details |

| Tactic Name | Privilege Escalation, Defense Evasion |

| Technique Name | Exploitation for Privilege Escalation; Hijack Execution Flow; Indicator Removal; Native API |

| Sub Technique Name | DLL, File Deletion |

| Attack Type | Vulnerability |

| Targeted Applications | Windows Common Log File System (clfs.sys); Microsoft Defender signature update interface; Windows client and server systems with CLFS authentication active |

| Region Impacted | Global |

| Industry Impacted | All industries using Windows client and server systems |

| IOC’s | hid.dll created in C:\Program Files\Common Files\microsoft shared\ink\ (file does not ship there); consent.exe loading a DLL from the ink directory; Defender signature update RPC (Proc42_ServerMpUpdateEngineSignature) called from outside the Defender service tree; MpEngine.dll created outside Defender installation paths; symbolic links under \BaseNamedObjects\Restricted\ (including mpasbase.vdm); SYSTEM conhost.exe on the interactive desktop after consent.exe termination |

| CVE | Not assigned (as of November 11, 2026) |

Recommended Actions:

  • Inventory the CLFS authentication state by querying HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication on all hosts; Mode 0 or 1 defines the population to prioritize, although the value alone does not establish that exploitation will succeed.
  • Do not disable CLFS authentication as a workaround, as this re-exposes systems to the older memory corruption bugs the mitigation was built to stop.
  • Restrict untrusted local code execution through application control, script control, and least privilege, as the exploit requires an existing local foothold.
  • Alert on any creation of hid.dll in C:\Program Files\Common Files\microsoft shared\ink, where the file does not ship with Windows, and on consent.exe loading a DLL from that directory.
  • Alert on Defender signature update RPC calls from callers outside the Defender service tree and on MpEngine.dll created outside Defender installation paths.
  • Hunt for Object Manager symbolic link creation and repointing under \BaseNamedObjects\Restricted\, including a link named mpasbase.vdm, and for osk.exe relaunched hidden by a user process.
  • Retain file creation, image load, and process creation telemetry, because the exploit deletes the planted DLL after use, and investigate any SYSTEM conhost.exe on the interactive desktop following a consent.exe termination.
  • Monitor Microsoft security updates for a fix and apply it when released; if compromise is suspected, isolate the host, preserve telemetry, and reset exposed credentials.

Reference:
https://www.cyderes.com/howler-cell/signdrop-zero-day