SignDrop exploit code claims to give Windows users SYSTEM access through CLFS

Executive Briefing
“Newly released SignDrop exploit code claims an ordinary Windows user can gain SYSTEM access...”
Key Takeaways
- 1.A researcher publishing as MSNightmare released SignDrop code and a write-up on GitHub. The code targets a log-authentication feature added to the CLFS driver.
- 2.According to the proof-of-concept code, a standard user prepares a CLFS log with user-controlled paths. When a privileged process opens it, the driver creates a .cnpf companion file under that process’s privileges, while SignDrop uses symbolic links to redirect where the file is created.
- 3.In the published code, the privileged process is the Defender antimalware service. The resulting file is created as SYSTEM but remains writable by the standard user; the researcher says this can be chained into a SYSTEM shell.
- 4.In an assessment published by 78researchlab’s Sungyup Nam, researcher Heewon Song reportedly found that the exploit works but is not reliable enough for operational use. The published chain requires Defender to be enabled.
- 5.The repository reports tests on Windows 11 26H2 and Experimental builds of Windows 11 26H2 and Windows Server 2025. Under the researcher’s claimed scope, systems with CLFS authentication mode set to 0 or 1 may be affected.
Newly released SignDrop exploit code claims an ordinary Windows user can gain SYSTEM access by exploiting how the CLFS driver creates a companion file. Microsoft has not confirmed the flaw or released a fix.
Key Developments and Technical Context
A researcher publishing as MSNightmare released SignDrop code and a write-up on GitHub. The code targets a log-authentication feature added to the CLFS driver.
According to the proof-of-concept code, a standard user prepares a CLFS log with user-controlled paths. When a privileged process opens it, the driver creates a .cnpf companion file under that process’s privileges, while SignDrop uses symbolic links to redirect where the file is created.
In the published code, the privileged process is the Defender antimalware service. The resulting file is created as SYSTEM but remains writable by the standard user; the researcher says this can be chained into a SYSTEM shell.
In an assessment published by 78researchlab’s Sungyup Nam, researcher Heewon Song reportedly found that the exploit works but is not reliable enough for operational use. The published chain requires Defender to be enabled.
The repository reports tests on Windows 11 26H2 and Experimental builds of Windows 11 26H2 and Windows Server 2025. Under the researcher’s claimed scope, systems with CLFS authentication mode set to 0 or 1 may be affected.
Strategic Analysis and Industry Implications
Disabling CLFS authentication is not a straightforward workaround. The source says it would remove a system from the claimed attack surface but also let CLFS process tampered logs, undoing protection against memory-corruption flaws.
The published chain has practical limits. Besides requiring Defender, the source says it alters UAC prompts in a way someone using the machine could notice.
Outlook and Key Factors to Watch
Microsoft has not confirmed the flaw, assigned a CVE or released a SignDrop fix. The source also reports no known attacks using it.
The repository claims the technique could work with other privileged antimalware engines, but that broader claim has not been tested.







