Public exploit code released in the week of the article claims that a local Windows user can gain SYSTEM privileges through the Common Log File System (CLFS) driver. The exploit, named SignDrop, targets the CLFS authentication mitigation in Windows and is described as converting a standard user token into NT AUTHORITY\SYSTEM. A researcher using the handle MSNightmare, also known as Nightmare Eclipse, posted the proof of concept on GitHub on November 10, 2026. Nightmare Eclipse has published numerous other Windows zero-days in recent months.
Status of the flaw
As of November 11, 2026, the SignDrop flaw had no CVE number and no patch. Microsoft has not confirmed the SignDrop claims. No independent validation or in-the-wild exploitation of SignDrop has been reported. The article's author expects Microsoft to review SignDrop and says a fix would probably come through a Patch Tuesday update.
How the attack is described
Naceri says SignDrop exploits a vulnerability in how clfs.sys handles creation of the.cnpf authentication file during the creation of a log file. The proof of concept targets a log-authentication feature added to the CLFS driver the year before the article. A standard user can create a log file, specify a path to an associated container in it, and coerce Windows Defender to open the file in the antimalware engine's context by calling the signature update RPC interface. In the published code, the privileged process used to trigger the exploit is the Defender antimalware service, triggered through its update interface.
According to the proof-of-concept code, when a privileged process later opens the prepared log, the driver creates the.cnpf companion file in that process's security context rather than the user's. As described, Defender then uses the container's file path to open the associated log file, and if that file is absent, a signature file is created with System privileges. SecurityWeek's reporting says that if the container of a CLFS log file is empty, CLFS attempts to sign it whether or not the signature file exists. The researcher claims the.cnpf file inherits the original log's permissions, producing a SYSTEM-created file the standard user can write to, which can be chained into a SYSTEM shell. The PoC in the researcher's post is claimed to spawn a SYSTEM shell on vulnerable systems.
Limits of the attack
SignDrop is a local privilege escalation bug, so an attacker must already be running code on the machine as a normal user. It cannot break in from the internet by itself. The Rocket Boys review says the SignDrop PoC does not work when CLFS authentication is turned off.
The CLFS mitigation
Microsoft added a hash-based message authentication code to CLFS log files, built from the file data and a secret key unique to each system. CLFS refuses to open a file if the code does not match. The mitigation shipped in Windows 11 25H2 and Windows Server 2025 updates released on or after October 28, 2025. Per Microsoft, new CLFS systems start in a learning mode that lasts 90 days from the first start with the updated driver, after which the driver moves to enforcement mode on its next start.
Who is exposed
According to the article, systems are affected when the CLFS authentication registry mode is 0 (enforced) or 1 (learning). A value of 2 or 3 means the mitigation is disabled and takes the system outside the claimed attack surface. Administrators can check the mode at HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication, where a Mode value of 0 or 1 falls within the researcher's claimed scope. Per Microsoft Learn, the authentication setting is on by default, and turning it off lets the driver open and parse any log file, including crafted ones. Microsoft says setting Mode to 2 lets CLFS parse potentially corrupted or malicious logfiles, restoring the memory corruption exposure the control was designed to remove, and the article advises administrators not to do so.
The researcher claims systems are exposed in either CLFS mode, so almost any machine older than 90 days would be vulnerable. Naceri states that Windows installations older than 90 days are generally vulnerable. The researcher estimates that about 80 percent of Windows installations are at risk, and this is an estimate rather than a measured count.
Testing and wider claims
The researcher reports testing SignDrop on Windows 11 26H2 and Windows Server 2025 lab setups. According to the repository, the exploit was tested on Windows 11 26H2, a Windows 11 26H2 Experimental build, and Windows Server 2025 Experimental. The researcher claims the vulnerability can be used against any antimalware engine to bypass its self-defense or tamper protection, and so to turn off any antivirus or EDR. The repository says the technique can work against any antimalware engine whose process runs with elevated privileges, but this broader claim has not been tested.