SignDrop: a public Windows exploit claims to turn a local user into SYSTEM, and Microsoft has not confirmed it or released a fix
Exploit code released on 10 November 2026 claims that a local Windows user can gain SYSTEM privileges through the Common Log File System driver. Microsoft has not confirmed the flaw, assigned a CVE or released a fix, and no attacks have been reported. What it needs, how to check your exposure and what to do meanwhile.
How urgent
Good to know
Who is affected
Windows machines where someone untrusted can already run code as a normal user (shared servers, remote desktop hosts, build machines); the researcher says it works with the CLFS authentication mode set to 0 or 1 and tested it on Windows 11 26H2 and experimental builds of Windows 11 26H2 and Windows Server 2025
What to do
No fix exists yet. Keep Windows updated and watch for Microsoft's advisory, do not run exploit code from the internet on machines that matter, and limit who can run code on shared Windows machines; administrators can read the CLFS authentication mode in the registry to see whether it falls within the claimed scope
Published 13 Nov 2026 · Sources last checked 13 Nov 2026No. 85 / 87
What happened
Public exploitExploit A piece of code or a technique that takes advantage of a specific flaw to get something the attacker should not get. Tap again to open the glossary code called SignDrop appeared on GitHub on Tuesday 10 November 2026, the same day Microsoft published its November security updates. The researcher, who publishes as MSNightmare, claims a standard Windows user can gain SYSTEM privileges through the Common Log File System (CLFS) driver, clfs.sys.
The Hacker News reports that Microsoft has not confirmed the flaw, has not assigned a CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary and has not released a fix.
What the sources say
- How it is claimed to work: the exploit targets a log-authentication feature added to the driver last year. When a privileged process opens a prepared log, the driver creates a companion file in that process's security context, and path redirection with object manager symbolic links lets the attacker choose where the file lands. In the published code the privileged process is the Defender antimalware service, triggered through its update interface. The result is a file created as SYSTEM that a normal user can write to, which the researcher says can be chained into a SYSTEM shell.
- What it needs: a local account that can run code. It is not a remote attack. The researcher says it works when the CLFS authentication registry mode is 0 (enforced) or 1 (learning).
- What was tested: Windows 11 26H2, an experimental Windows 11 26H2 build and an experimental Windows Server 2025 build, according to the repository. The claim that it works against any antimalware engine running with elevated privileges has not been tested.
- Status: no CVE, advisory or patchPatch (security update) A fix released by the maker of a piece of software to close a flaw or a bug. Tap again to open the glossary appeared in the November updates. It is not in CISA's known exploited vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary catalog and no attacks using it have been reported. CLFS has had ten flaws in that catalog before.
Why it is "good to know" and not an emergency
An attacker already needs to run code on the machine. For a laptop you alone use, the risk is low. It matters on machines where several people or untrusted programs run code: shared servers, remote desktop hosts and build machines. Treat it as a flaw to watch until Microsoft answers.
What to do
- Keep Windows updated and watch for a Microsoft advisory or CVE for CLFS.
- Limit who can run code on shared Windows machines, and do not run exploit code from the internet on machines that matter.
- Check your exposure if you administer Windows machines: The Hacker News says the CLFS authentication mode is under
HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication, and aModevalue of 0 or 1 falls within the researcher's claimed scope. Microsoft's guidance describes that setting and the risks of disabling it: read it before changing anything. Do not change the setting on production machines on our word alone.
What we could not confirm
We read The Hacker News' report only. We did not read the researcher's repository or write-up, or any statement from Microsoft, and we did not run the exploit. We could not confirm that the technique works as described, which Windows versions are really affected, or whether a fix is coming.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.