
SignDrop is a new Windows privilege escalation exploit with public code and no patch yet. It only works on PCs where CLFS logfile authentication is active, and you can check that in under a minute: read the Mode value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CLFS\Authentication. A 0 or 1 puts your PC in range. Don't switch the protection off. Keep Microsoft Defender updated and stop running programs you don't trust until Microsoft ships a fix.
What happened with SignDrop
On November 10, 2026, the researcher Abdelhamid Naceri (Nightmare Eclipse, MSNightmare on GitHub) published SignDrop with working proof-of-concept code. That was the same day Microsoft released its November security updates, and those updates contain nothing for it. There is no CVE yet.
The bug sits inside a protection Microsoft added on purpose. Since October 28, 2025 (KB5056852), Windows signs Common Log File System (CLFS) log files with an authentication code, so the driver refuses logs that something else has tampered with. Each signed log gets a companion file ending in .cnpf, and Microsoft's documentation says that file "is created with the same security attributes as the file it provides recovery information for."
SignDrop abuses exactly that. A standard user prepares a log file, then tricks a process running as SYSTEM, Microsoft Defender in the published code, into opening it. The companion file is then created with SYSTEM rights but with permissions the user controls. Chained correctly, that ends in a SYSTEM shell. In the researcher's words, "Everything is done properly by Microsoft here but the logic allows abuse."
One thing worth keeping in proportion: this is a local attack. Someone has to run code on your PC first, through malware you opened or an account they already have. It is the second step of an attack, the one that turns a normal user into full control of the machine.
Which Windows versions are affected
Microsoft lists the CLFS authentication feature for Windows 11 version 25H2, Windows 11 version 26H1 and Windows Server 2025. The researcher says he tested SignDrop on Windows 11 26H2 and on preview builds of 26H2 and Server 2025.
The registry value is what decides it. Microsoft documents four values:
- 0: the mitigation is enforced. In range for SignDrop.
- 1: learning mode. Also in range.
- 2: an administrator disabled it.
- 3: the system disabled it automatically.
A PC starts in learning mode when it first gets the feature and moves to enforcement after a 90-day adoption period. Not every machine ends up in range, though. Dormann, quoted by Ars Technica, found only one of his many machines that met the requirement.
How to check if your PC is exposed, step by step
- Check your Windows version first. Right-click Start, choose Windows Settings, select System and pick About. Under Windows specifications, note the version (25H2, 26H1, 26H2).
- Press Windows + R, type
regeditand press Enter. Accept the User Account Control prompt. - In the left pane, open HKEY_LOCAL_MACHINE
- Paste
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CLFS\Authenticationinto the address bar at the top and press Enter. gt; SYSTEM - Paste
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CLFS\Authenticationinto the address bar at the top and press Enter. gt; CurrentControlSet - Paste
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CLFS\Authenticationinto the address bar at the top and press Enter. gt; Services - Paste
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CLFS\Authenticationinto the address bar at the top and press Enter. gt; CLFS - Paste
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CLFS\Authenticationinto the address bar at the top and press Enter. gt; Authentication.
- Look at the Mode value in the right pane. A 0 or 1 means the PC is in range. Close the Registry Editor without changing anything.
- If you prefer PowerShell, open it and run
Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\CLFS\Authentication" -Name Mode. It shows the same value and changes nothing. - Update Defender now. Open the Windows Security app, select Virus & threat protection > Protection updates > Check for updates. Microsoft says Defender blocks potential exploitation attempts and that it has no evidence of attacks so far.
- Install the fix when it lands. Go to Start > Settings > Windows Update > Check for Windows updates, then Download & install. The next scheduled Patch Tuesday is December 8, 2026. Microsoft hasn't said if the fix will be in it, and it could come earlier.
Until then, the practical rule is simple. Don't run downloaded tools, cracks or "PoC to test your PC" files from GitHub. Running the exploit to check yourself is exactly the kind of code this flaw needs.
If it still doesn't work
- There is no Authentication key at all. The feature most likely isn't on that PC. Windows 10, Windows 11 24H2 and older releases aren't in Microsoft's list for it.
- Protection updates fail in Windows Security. Download the security intelligence installer for your PC (x64 for most PCs, ARM64 for ARM devices) from Microsoft's Defender updates page, run the .exe, then check that the version and "last updated" time changed. Note the error code if it still fails.
- Windows Update throws an error. November's cumulative update has had install failures on some PCs. Our guide to fixing KB5132061 when it fails to install covers the usual fixes, and you'll want that working before the SignDrop patch arrives.
- The registry editor won't open on a work PC. Your IT team controls this setting through Group Policy or Intune. Send them the registry path and leave it to them.
Video: New SignDrop Zero-Day Exploit Turns Windows CLFS Security Feature Into SYSTEM Access
Video by TechIn60.
Quick answers
Is there a patch for SignDrop?
No. As of November 16, 2026, Microsoft hasn't published a fix, an advisory or a CVE. It told Ars Technica it is investigating the write-up. Watch the Microsoft Security Update Guide and Windows Update.
Should I set Mode to 2 to block SignDrop?
No. Setting 2 takes the PC out of SignDrop's range, but Microsoft says it doesn't recommend disabling the mitigation, because CLFS then parses "potentially corrupted or malicious logfiles." That reopens the older CLFS memory corruption bugs the feature was built to stop. Even the researcher advises against it. The details are on Microsoft's CLFS authentication mitigation page.
Is SignDrop related to Memory Integrity turning on?
No, they are separate features. If a recent update switched on Memory Integrity and you're wondering whether to keep it, read what Memory Integrity does and when to leave it on.