
AI-generated illustration
SignDrop Zero-Day: Windows 11 Still Has No Patch
The SignDrop zero-day lets a standard Windows user climb to SYSTEM access, and Microsoft has not released a fix. A researcher who goes by MSNightmare posted the exploit on GitHub on 10 November, the same day as the November security updates. Microsoft has not confirmed the flaw or given it a CVE number. No attacks have been reported so far.
Update (16 November 2026): Microsoft had not issued a CVE, advisory or patch at the time of writing.
What Is the SignDrop Zero-Day?
SignDrop is public proof-of-concept code that abuses the Common Log File System (CLFS) driver, clfs.sys. A local user with normal rights can use it to gain SYSTEM, the highest privilege level on Windows. That access could let an attacker switch off security tools.
This is a local attack, not a remote one. The attacker needs to be on the machine first, through a stolen login or a separate foothold. Windows security has had a rough run lately, including a bootkit that bypasses Secure Boot on patched systems.
How Does the Exploit Work?
Microsoft added log authentication to CLFS in October 2025. The driver attaches a code to each log, so it only parses logs it wrote itself.
The bug sits in a companion recovery file with the .cnpf extension. When a privileged process opens a prepared log, the driver creates that file using the process’s own security rights. A standard user controls the file paths. Symbolic links then redirect the new file to a spot the attacker picks.
In the published code, the privileged process is the Microsoft Defender antimalware service. The new file inherits the log’s permissions. That gives the user write access to a file SYSTEM created, and the researcher chains it into a SYSTEM shell.
Which Windows Versions Are Affected?
The researcher tested Windows 11 26H2, an experimental 26H2 build and an experimental Windows Server 2025 build. A system is in scope when the CLFS authentication Mode value is 0 (enforced) or 1 (learning).
Systems older than about 90 days usually move from learning to enforcement on their own. So most established installs sit in the targeted setup. Defender must be running for the published chain to work.
How Serious Is It?
It is serious, but not at emergency level yet. Sungyup Nam of 78researchlab reported that a colleague, Heewon Song, confirmed the exploit works. Song judged it too unreliable for real attacks. Running it also changes every UAC prompt to show two shells, so a user would notice. The repository says it works against any elevated antimalware engine. Nobody has tested that claim.
Still, CLFS has a bad history. CISA lists 10 CLFS flaws as exploited, and one fed ransomware campaigns in April 2025. The same researcher has also dropped several Windows and Defender exploits since April. Microsoft patched RoguePlanet (CVE-2026-50656) in July and ShieldBreak (CVE-2026-69414) in August. Three of the researcher’s earlier Defender flaws saw use in attacks.
What Should You Do Now?
You cannot patch this one yet, so focus on limiting the risk.
- Check the Mode value. Open the registry key HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication and read Mode. A 0 or 1 puts the PC in scope.
- Leave the mitigation on. Modes 2 and 3 switch it off. Doing that reopens older CLFS memory corruption bugs, so skip it.
- Limit local access. Fewer people with interactive logins on sensitive machines means fewer people who can run the exploit.
- Watch for tampering. Look for odd privilege changes and any attempt to disable Defender or other security tools.
- Keep installing fixes. Microsoft’s other recent patches still matter, like the emergency .NET update for the Brotli flaw.
Watch the Microsoft Security Update Guide for a response.
Sources: The Hacker News, TechSpot