A researcher has published working exploit code for a new, unpatched Windows flaw called SignDrop. It lets a program running with ordinary user rights take full control of a PC by running a command prompt as SYSTEM, the built-in account Windows uses for its core processes. Unusually, it turns one of Microsoft's own security fixes, and Microsoft Defender, into part of the attack.
Forge PC has not tested SignDrop and we do not recommend running exploit code on your own PC. This story is based on reports from Ars Technica, SecurityWeek and TechSpot and on Microsoft's documentation, checked on 16 November 2026.
What happened
On Tuesday 10 November, a researcher using the name Nightmare Eclipse published SignDrop on GitHub, just as Microsoft was rolling out its November security updates. TechSpot identifies the researcher as Abdelhamid Naceri, a former Microsoft employee who has released several earlier Windows exploits.
The bug is in the Common Log File System (CLFS), a logging service used by apps and drivers across Windows. Last year Microsoft added "logfile authentication" to CLFS to stop attackers abusing tampered log files. According to Ars Technica and SecurityWeek, SignDrop tricks Defender, which runs with the highest privileges, into opening a log file prepared by the attacker through a legitimate signature-update function. CLFS then creates an authentication file with Defender's SYSTEM-level rights, but with permissions the attacker controls, and that becomes a route to a SYSTEM command prompt.
This is a "local privilege escalation" bug. On its own it doesn't let someone break into your PC over the internet. The risk is that malware which arrives another way, such as a dodgy download, cheat tool or cracked game, could use it to gain full control and switch off security software.
Who is affected
The researcher says it was tested on Windows 11 26H2 and experimental builds of Windows 11 and Windows Server 2025. Independent testing is narrower:
Vulnerability analyst Will Dormann told Ars Technica he could reproduce it, but only on Windows 11 26H2 systems that had existed for more than 90 days. A fresh 26H2 install with updates didn't work.
He said the registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CLFS\Authentication\Mode must be 0 or 1. Microsoft's documentation says 0 means the mitigation is enforced and 1 means it is in learning mode, adding authentication codes to existing logs; 2 means an administrator has disabled it.
Only one of the many machines Dormann uses met all the requirements.
You can see which version of Windows you're running by typing winver in the Start menu. If you've not moved to 26H2 yet, our guide to updating to Windows 11 26H2 explains the staged rollout.
What Microsoft says
Microsoft told SecurityWeek it is "actively investigating" and will update affected products "as soon as possible". It says Microsoft Defender detects and blocks exploitation of the vulnerability and alerts on the related behaviour, and that it has not seen the flaw being exploited in the wild. TechSpot notes a fix may not arrive before December's Patch Tuesday on 8 December unless Microsoft releases it early.
What you should do
Keep Microsoft Defender (or your antivirus) on and up to date. Microsoft says Defender already blocks this attack. Our Defender vs paid antivirus comparison explains what Defender covers.
Install Windows updates as soon as a fix arrives, and keep an eye on December's Patch Tuesday. Our November 2026 Windows update coverage has details of this month's patches.
Don't run untrusted software. Privilege escalation bugs are most dangerous when combined with something you've installed yourself, such as cheats, "free" game keys or cracked apps.
Use a standard user account for everyday use where you can, and avoid approving admin prompts you didn't expect.
Don't switch off the CLFS mitigation. Microsoft's documentation says disabling logfile authentication is not recommended, because CLFS would then parse potentially corrupted or malicious log files without checks, re-opening the door to the older attacks it was designed to stop.
Have a backup. If anything goes wrong, a recent backup makes recovery much easier. See how to back up Windows 11.
Our verdict
SignDrop is a serious bug with public exploit code, but the conditions for it to work appear narrow, Microsoft says Defender blocks it, and there's no evidence yet of attacks in the wild. For home users and gamers the sensible response is simple: keep Defender on, avoid untrusted downloads, don't tinker with the CLFS mitigation, and install Microsoft's fix when it arrives. Forge PC has not tested the exploit.