Last updated: 15 November 2026, 08:13 IST. Sources are at the end.
SignDrop is a Windows zero-day that a researcher published on 10 November 2026 together with working exploit code. It lets someone who can already run a program on a PC or server as a normal user become SYSTEM, the most powerful local account. Microsoft has not released a fix, a CVE number or an advisory. Nobody has reported attacks that use it so far. This guide explains who is exposed, how to check a machine and what to do until a patch arrives.
Not sure whether your servers or your vendor’s tools are exposed? Emergency exposure check, ₹2,999, 48 hours. Send us up to 5 hosts or product versions and get a written verdict for each, what to patch first and how to verify the fix. Book the check or ask a question first.
The short answer
- SignDrop does not work over the network on its own. An attacker first has to run code on the machine, for example through a phishing attachment or a stolen password.
- According to the reports, the exposed systems are Windows 11 25H2 and later and Windows Server 2025, where the CLFS logfile authentication feature is active. Windows 10 and Windows Server 2022 do not have that feature.
- Do not switch the feature off as a fix. Switching it off removes a protection against older CLFS attacks. Microsoft’s guidance and the researcher both advise against it.
- Limit who can run untrusted programs, start with shared servers, and install Microsoft’s fix when it ships. The next scheduled Windows updates are due on 8 December 2026.
What SignDrop is
CLFS, the Common Log File System, is the Windows component that programs use to write log files. Since October 2025 Windows signs these log files, so that the driver can reject a file someone has tampered with. For the signing, Windows creates a small companion file with the ending .cnpf next to the log.
SignDrop abuses the way Windows creates that companion file. A process that runs as SYSTEM opens a log file the attacker has prepared. The driver then creates the companion file with the rights of that process, and the attacker redirects where the file lands. The published code uses Microsoft Defender’s own service as the SYSTEM process and triggers it through the signature update interface. The attacker ends up with a SYSTEM command prompt.
The researcher publishes under the name MSNightmare. Microsoft confirmed two earlier releases from the same researcher: RoguePlanet in June (CVE-2026-50656) and ShieldBreak in August (CVE-2026-69414). The Hacker News adds that attackers have used three of the researcher’s earlier Defender flaws. That record is the reason to take this claim seriously before Microsoft confirms it.
Is SignDrop being exploited?
Nobody had reported an attack when we checked on 15 November. This is what each party has said:
- Microsoft: no statement on SignDrop, no CVE and no fix. The November updates came out on the same day and contain nothing for it.
- CISA: SignDrop is not on the Known Exploited Vulnerabilities list, according to The Hacker News on 12 November.
- Independent test: The Hacker News reports that a researcher at PurpleHound ran the exploit and confirmed that it works. He judged it not reliable enough for real operations.
- Side effect: the same report says the exploit changes every UAC prompt on the machine, which makes an attack easy to notice.
- Unverified claim: the researcher says the technique could switch off any antivirus or EDR product. No vendor has confirmed that.
Who is exposed to SignDrop
| System | Exposed? |
|---|---|
| Windows 11 25H2 and 26H1 with updates from 28 October 2025 or later | Yes, while the CLFS setting is 0 or 1 |
| Windows Server 2025 with the same updates | Yes, while the CLFS setting is 0 or 1 |
| Windows 11 26H2 test builds | Yes, the researcher tested on these |
| Windows 10, Windows 11 24H2 and earlier, Windows Server 2022 and earlier | Not on Microsoft’s list for this feature, according to ThreatDefence |
Look at these machines first:
- Servers where many people log on, such as Remote Desktop session hosts, virtual desktops and jump hosts.
- Application and database servers that run code on behalf of other people.
- Office PCs, where a phishing attachment runs with the user’s rights.
How to check a machine
Open PowerShell as an administrator and read the CLFS setting:
Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\CLFS\Authentication' | Select-Object Mode, EnforcementTransitionPeriod, LearningModeStartTimeWe took this check from the reports listed under Sources, which describe Microsoft’s CLFS documentation. We have not run it in our own lab, because the lab has no machine on Windows 11 25H2.
| Mode | Meaning | Exposed to SignDrop? |
|---|---|---|
| 0 | Enforced | Yes |
| 1 | Learning | Yes |
| 2 | Switched off by an administrator | No, but the CLFS protection is off |
| 3 | Switched off by Windows itself | No, but the CLFS protection is off |
If the registry key does not exist, the Windows build does not have the feature. New devices start in learning mode and move to enforcement after 90 days.
Do not run the public exploit on a work machine to test it.
What to do until Microsoft ships a fix
- Leave CLFS authentication switched on.
- Restrict untrusted programs. Use App Control for Business or AppLocker on servers and shared machines. Turn on the Defender attack surface reduction rule that blocks executable files unless they meet a prevalence, age or trusted-list rule.
- Harden shared servers first. Limit who may log on to session hosts and jump hosts, and block programs from running out of folders that users can write to.
- Treat a silent security tool as an incident. If antivirus or EDR stops, loses real-time protection or reports tampering on an affected build, look into it the same day.
- Record the Mode value across your PCs, so that a change stands out.
- Install Microsoft’s fix when it is out. It could arrive before 8 December.
Signs of SignDrop use to look for
ThreatDefence published hunting ideas on 13 November. They are starting points for a search and not proof of an attack:
- A file ending in .cnpf in a place where it does not belong, such as System32, Program Files or the Defender folder under ProgramData.
- A .cnpf file written by a Defender process such as MsMpEng.exe.
- A cmd.exe or powershell.exe that runs as SYSTEM while its parent is an ordinary user’s process.
- Defender event 2001 (definition update failed) at a time when no update was due, followed by event 5001 (real-time protection disabled) or 5013 (tampering blocked). You find these in the log Microsoft-Windows-Windows Defender/Operational.
- A change to the Mode value that nobody on your team made.
If you find the jump to SYSTEM on a machine, isolate it and keep the evidence. Then reset the passwords of every account that was signed in there, service accounts included.
If an IT provider manages your PCs
Send them three questions:
- Which of our machines run Windows 11 25H2 or later, or Windows Server 2025?
- Who can run programs on our shared servers, and is AppLocker or App Control in use there?
- Will you install the December Windows updates within a week of release?
Related guides
Need help finding unpatched and exposed systems? Our VAPT services find them before attackers do, and the free website safety check grades your site in seconds. Contact us for a quote.
Sources
- The Hacker News: New SignDrop zero-day exploit turns Windows CLFS security feature into SYSTEM access, 12 Nov 2026
- ThreatDefence: Windows SignDrop CLFS zero-day, mitigation and hunting, 13 Nov 2026
- Microsoft Support: CLFS Authentication Mitigation, KB5056852, 28 Oct 2025 (cited by ThreatDefence; we did not read it directly)
