SignDrop Exploit Turns Microsoft's CLFS Hardening Into a SYSTEM Path
Security / news
SignDrop Exploit Turns Microsoft's CLFS Hardening Into a SYSTEM Path
The proof of concept works only on machines where the 2025 log-file authentication mitigation is switched on, and Microsoft has said only that it is investigating.

A public proof of concept called SignDrop, posted to GitHub under the name MSNightmare, gives a local unprivileged user a SYSTEM shell on Windows machines that run Microsoft's Common Log File System (CLFS) authentication mitigation. It has no CVE, and Microsoft said it is investigating.
The Hacker News, in its Nov. 16 weekly recap by Ravie Lakshmanan, attributed the release to the researcher Abdelhamid Naceri, who also goes by Chaotic Eclipse. The repository itself gives only the handle. At the time of fetching it showed 496 stars, 131 forks, seven commits and an MIT licence, and it carries no date of publication.
The mitigation is the attack surface
CLFS is the Windows kernel driver, clfs.sys, that manages transaction log files. Microsoft's support page, first published Oct. 28, 2025, says the mitigation adds HMAC authentication codes (keyed hashes that prove a log file was written by the local system) so that CLFS refuses tampered files. The Hacker News reported that the bug class this blocks made up 19 of 24 CLFS CVEs over five years.
The README says SignDrop abuses how clfs.sys creates the .cnpf signature file. The driver creates it as SYSTEM at a path the attacker chooses, and the attacker then replaces its contents with a payload DLL. Cyderes said the flaw "turns a defense into an attack surface," according to the recap.

Which machines are exposed
Exposure follows a registry value, HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication\Mode. The README says a machine is vulnerable when Mode is 0 or 1 and not vulnerable when it is 2 or 3. Microsoft's page defines those values the other way round from a safety point of view.
| Mode | Microsoft's meaning | SignDrop README |
|---|---|---|
| 0 | Enforced | Vulnerable |
| 1 | Learning | Vulnerable |
| 2 | Disabled by administrator | Not vulnerable |
| 3 | Disabled by system | Not vulnerable |
A fresh system starts in Mode 1 and moves to Mode 0 after a 90-day adoption period, so a default install is exposed on the README's account for its whole life. Microsoft's page applies the mitigation to Windows 11 versions 25H2 and 26H1 and to Windows Server 2025, in updates released on or after Oct. 28, 2025. The README lists Windows 11 26H2, a 26H2 experimental build and a Server 2025 experimental build as tested, and 26H2 does not appear on Microsoft's page as fetched.
The author claims about 80 percent of Windows installations are vulnerable. That figure is the author's and the repository gives no method for it, and The Terminal did not run the code.
Why turning it off is not the fix
The README says there is no workaround short of a Microsoft patch. Setting Mode to 2 would stop SignDrop but, the author writes, exposes the machine to the other CLFS memory-corruption bugs the mitigation exists to block. CISA's catalog lists at least eight CLFS entries, the latest being CVE-2025-32701 (added May 13, 2025, due June 3, 2025), so that exposure is not theoretical.
A local privilege escalation needs a foothold first, which is why such bugs tend to appear in the second stage of an intrusion. A listing of this one would carry a short clock: the BOD 26-04 deadline analysis found 120 of 152 entries given three days. Defenders can also compare the pattern with the Mark of the Web bypass exploited this autumn, another case of a Windows protection becoming the route in.
Until Microsoft assigns a CVE, there is nothing to patch and nothing to search for in the Update Guide. The README directs concerns to secure@microsoft.com, and the next signal is whether the Mode 0 and Mode 1 behaviour appears in a Microsoft advisory.
Sources
More in Security
- 01SAP Patches ICM2SHELL and PROXYGATE, Two CVSS 10.0 Pre-Auth BugsOnapsis found both flaws, reports no exploitation as of Nov. 12, and says the SAP Gateway bug depends on an access-control file most sites never tightened.
- 02Bridgewater's 11-Day Exploit Claim Meets CISA's 2026 Catalog DataThe catalog confirms more additions and a higher share of new bugs, but it records when CISA listed a flaw rather than when attackers first used it.
- 03GPGME's CVE-2026-129975 Double Free Needs Only a Crafted Key, and 2.3.1 Is the FixGnuPG disclosed five days early because GitLab had to update, and no CVSS score exists yet to rank it.
- 04Dragos Seeded 2 Million Prompts With Canaries; Amazon's Decoys Caught ARTEX Agents Grading Stolen AI KeysTwo reports from November 13 and 19 show AI credentials being harvested and spent by machines, and a Chinese lab fetching secrets from ZDR prompts.