Frames and Fans
Live
Handhelds & consoles

SignDrop Zero-Day Exploits Windows CLFS Authentication Flaw

Security researcher Abdelhamid Naceri published a SignDrop proof-of-concept on November 10, 2026, demonstrating a Windows CLFS driver vulnerability that allows standard users to gain SYSTEM privileges.

Security researcher Abdelhamid Naceri published a SignDrop proof-of-concept on November 10, 2026, demonstrating a Windows...

A newly disclosed Windows zero-day exploit named SignDrop abuses a critical flaw in the Common Log File System (CLFS) driver. The vulnerability allows a local user to elevate privileges to full SYSTEM access by manipulating a security mechanism Microsoft designed to prevent such attacks.

Security researcher Abdelhamid Naceri, also known online as Nightmare Eclipse or MSNightmare, published the proof-of-concept code on GitHub. The exploit targets how the clfs.sys driver handles the creation of authentication files. When a new log file is created, CLFS can generate a signature file (.cnpf) with SYSTEM privileges while retaining attacker-controlled file permissions. If a privileged process like Windows Defender is later forced to open the log file, the authentication file is created with elevated rights.

This flawed logic lets an attacker place a payload that spawns a SYSTEM shell. The machine is vulnerable if the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CLFS\Authentication\Mode has a value of 0 (enforcement mode) or 1 (learning mode). Naceri states users are generally vulnerable if their Windows installation is older than 90 days, estimating SignDrop should work on 80% of the world's Windows installations. Microsoft introduced this CLFS logfile authentication in October 2025 to Windows 11 25H2, 26H1, and Windows Server 2025 to limit tampering.

Technical details of the vulnerability

The flaw stems from improper handling of authentication files during log file creation. The code responsible for opening container and log files always opens the container if the original log file is opened. If the container is empty, CLFS attempts to sign it regardless of whether a signature file already exists.

This allows an attacker to abuse the mechanism. They can create a signature file at a controlled location and then reopen the file to insert a payload. The vulnerability can bypass any antimalware engine's self-defense or tamper protection by triggering file creation within the context of the engine's own legitimate process. Independent researchers have reported some compatibility and reliability limitations with the proof-of-concept. Cyderes successfully compiled and tested it but found no evidence of zero-day exploitation in the wild.

Microsoft's response and mitigation status

Microsoft is actively investigating the reported vulnerability. The company has found no evidence of active exploitation in the wild. Microsoft Defender can detect and block exploitation attempts and will alert on the associated privilege-escalation behavior.

A Microsoft spokesperson stated, "Microsoft Defender can detect and block exploitation attempts, adding that it has found no evidence of active exploitation in the wild." SignDrop has not yet received an official CVE designation or a dedicated security patch. Microsoft published its November security updates on the same day the proof-of-concept was released but did not confirm the flaw or release a fix.

There is currently no solution except waiting for a Microsoft patch. Disabling the CLFS mitigation would expose devices to other memory corruption vulnerabilities. CLFS provides logging services inside Windows and has been a target for years; ten CLFS flaws already appear in the CISA Known Exploited Vulnerabilities catalog.

Naceri is a former Microsoft employee who has disclosed multiple zero-day flaws in Microsoft components since April. These include BigDiskBuster, ShieldCrash, and RoguePlanet. Microsoft has fixed some, like ShieldBreak and GreenPlasma, but others lack official patches. The company previously warned of legal action against anyone causing real harm after Naceri's public zero-day disclosures. Microsoft's investigation continues, with updates for impacted products planned as soon as possible.

Related coverage

More from Handhelds & consoles