Windows “SignDrop” zero-day: unpatched flaw gives attackers SYSTEM rights

A researcher published a working exploit for a Windows CLFS driver flaw that turns a normal user into SYSTEM. There is no patch yet — here is how to reduce the risk.

Publicly disclosed: 12 November 2026

On 12 November 2026 security researcher Abdelhamid Naceri (“Nightmare Eclipse”) published SignDrop, a working exploit for an unpatched Windows privilege escalation. It abuses the way the Common Log File System (CLFS) driver creates the authentication file for a new log — the protection Microsoft added in October 2025. Anyone who can already run code as a normal user can become SYSTEM, the highest level on Windows. No CVE has been assigned and Microsoft has not released a fix.

The researcher tested it on Windows 11 26H2 and Windows Server 2025 and estimates that about 80% of Windows installations are vulnerable. Exploitation in real attacks has not been reported yet, but public exploit code usually reaches ransomware groups within days: they use such flaws after phishing or a stolen password to disable antivirus and spread across the network.

How to check

According to the researcher, a computer is vulnerable when the registry value HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication\Mode is 0 or 1 (learning or enforcement mode). Do not run the published exploit on production machines to “test” them. Do not switch the CLFS protection off either — that re-opens older memory-corruption attacks.

What to do until Microsoft patches it

  1. Make sure everyday user accounts are not local administrators, and remove old or shared admin accounts — see least privilege.
  2. Block unknown programs with application control (Microsoft Defender Application Control, AppLocker or your EDR), especially in the Downloads and Temp folders.
  3. Make sure EDR/antivirus is active and alerting on every workstation and server, and watch for SYSTEM processes started from user programs.
  4. Treat phishing and stolen-password alerts as urgent: this exploit needs the attacker to be on the machine already.
  5. Install Microsoft’s fix as soon as it is released — follow your patch process and test on a few machines first.

A local flaw is still serious: it turns one infected laptop into full control of that machine.

Sources: BleepingComputer, 12 Nov 2026.

Need help with this? Contact CySec for a consultation.


All articles

Need help with this?

Our engineers can review your current setup and propose concrete improvements.