SignDrop Zero-Day Turns Windows' CLFS Shield Against Itself

SignDrop, an unpatched Windows zero-day, abuses Microsoft's own CLFS log-authentication mitigation to gain SYSTEM privileges.

@sharedot

SignDrop Zero-Day Turns Windows' CLFS Shield Against Itself

By @sharedot · · 8 pages

  • Cybersecurity
  • Windows
  • Zero Day
  • Clfs
  • Privilege Escalation

SignDrop, an unpatched Windows zero-day, abuses Microsoft's own CLFS log-authentication mitigation to gain SYSTEM privileges.

What happened: a public zero-day with no patch

On Tuesday, the same day Microsoft shipped its November security updates, a researcher publishing as Nightmare Eclipse (also known as MSNightmare) released a proof-of-concept exploit called SignDrop on GitHub with a detailed writeup.

The exploit targets the Windows Common Log File System (CLFS) driver and claims to let any local standard user escalate to SYSTEM, the highest privilege level on the machine.

According to The Hacker News, Microsoft has not confirmed the flaw, assigned a CVE, or released a fix, and no patch appeared in the November updates. No attacks using the exploit have been reported, and the CISA Known Exploited Vulnerabilities catalog does not list it.

The twist: a defense becomes the attack path

The surprise is that SignDrop abuses the very mitigation Microsoft built to protect CLFS.

In October 2025, Microsoft added log-file authentication to the driver in Windows 11 25H2, 26H1 and Windows Server 2025, attaching a hash-based message authentication code computed from log data and a machine-unique key.

The exploit targets how clfs.sys creates the companion .cnpf recovery file when a privileged process opens a prepared log. By redirecting that file creation with Object Manager symbolic links, a standard user gets a SYSTEM-owned file that inherits the original log's permissive DACL.

'Everything is done properly by Microsoft here but the logic allows abuse,' the researcher wrote.

Defender used as the privileged trigger

The published chain coerces Windows Defender into opening the attacker's prepared log by calling ServerMpUpdateEngineSignature, a legitimate function for processing antivirus signature updates.

Because the file-creation request appears to come from Defender's own elevated process, it passes tamper-protection checks.

According to Security Affairs, the researcher claims the technique could work against any antimalware engine with a privileged process, potentially defeating self-defense mechanisms across security products — though that broader claim has not been tested.

Defender must be enabled for the chain to succeed, and running the exploit converts every UAC prompt into a user shell and a SYSTEM shell, making the attack highly visible at the machine.

The evidence: independently confirmed, but unreliable

The exploit was tested on Windows 11 26H2, a Windows 11 26H2 Experimental build, and Windows Server 2025 Experimental.

Independent testing backs the core claim: according to The Hacker News, Sungyup Nam, head of research at Korean firm 78researchlab, reported that researcher Heewon Song of the firm's PurpleHound team tested the exploit and found that it works, though he assessed it is not reliable enough for operational use.

Researcher Will Dormann told Ars Technica he reproduced the exploit, but only on one of his many machines, noting it seems to require Windows 26H2 that has existed for more than 90 days. According to SecurityWeek, provider Cyderes also compiled and tested the PoC successfully.

Who is exposed — and the 80% claim

Systems are in scope when the CLFS authentication mode registry value at HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication is 0 (enforced) or 1 (learning).

Because installations older than 90 days typically move automatically from learning to enforcement, established machines sit squarely in the claimed attack surface.

Administrators should not disable the mitigation (mode 2 or 3) to escape: both the researcher and Microsoft's documentation warn that disabling lets CLFS parse tampered log files, reopening the memory-corruption flaws the protection was built to stop.

According to Security Affairs, the researcher's own advice is to wait for a Microsoft patch.

What comes next: watching for a Microsoft response

Microsoft told SecurityWeek it is actively investigating the reported vulnerability, that Defender detects and blocks exploitation attempts, and that it has not observed exploitation in the wild.

The researcher, whom Security Affairs identifies as Abdelhamid Naceri, has a track record here: his earlier Defender exploit RoguePlanet was confirmed as CVE-2026-50656 and patched in July, and his ShieldBreak bypass became CVE-2026-69414, with three of his earlier Defender flaws exploited in attacks.

SignDrop is a different class, targeting the CLFS driver's authentication feature rather than race conditions in Defender's file handling. Microsoft's security update guide and the CISA catalog are the places to watch for a formal response or signs of real-world abuse.

Sources

  1. thehackernews.com › New SignDrop Zero-Day Exploit Turns Windows CLFS Security Feature Into SYSTEM Access
  2. securityweek.com › Nightmare Eclipse Drops Windows Zero-Day Exploit 'SignDrop'
  3. arstechnica.com › Windows 0-day dropped by disgruntled researcher hands hackers System rights
  4. securityaffairs.com › New SignDrop Exploit Can Abuse Windows Defender to Bypass Security Protections

More on Cybersecurity