Itdaily - Windows zero day SignDrop gives local users System privileges

Windows zero day SignDrop gives local users System privileges

ThinkPad X1 Carbon Gen 14 Aura Edition opened, showing the Windows 11 Start menu on screen.

A researcher using the pseudonym Nightmare Eclipse has disclosed a new Windows zero day. SignDrop lets an ordinary local user obtain System privileges. Microsoft is investigating the report.

The researcher published SignDrop last Tuesday. Nightmare Eclipse has long been openly at odds with Microsoft and has already released several Windows zero days in recent months.

The vulnerability lies in the Common Log File System (CLFS), a logging service that Microsoft describes as a general-purpose logging service for software running in user mode or kernel mode.

Defender as a weapon

An attacker with ordinary user privileges forces a privileged process, such as Windows Defender, to open a specially crafted CLFS container. The exploit uses ServerMpUpdateEngineSignature for this, a Defender function for updating antivirus signatures. Through symbolic links in the Windows Object Manager, opening the container takes place in the security context of the antimalware engine.

If the associated authentication file is missing, CLFS creates it with Defender’s System privileges. Because the new file inherits the access list of the original file, the attacker gains access to a file that was created with System privileges.

The flaw stems from a security measure that Microsoft introduced in October 2025 against other CLFS vulnerabilities. Nightmare Eclipse writes that Microsoft did everything correctly, but that the logic allows abuse. According to the researcher, the approach also works against other antimalware engines and can disable antivirus or EDR software.

Which systems are vulnerable?

According to Nightmare Eclipse, the exploit works on Windows 11 26H2, Windows 11 26H2 Experimental and Windows Server 2025 Experimental. A system is vulnerable if the CLFS authentication mode is set to learning mode or enforcement mode. That is the case if the registry value Mode under CLFS\Authentication is set to 0 or 1.

Researcher Will Dormann was able to reproduce the exploit, but not on all versions of Windows 11, reports Ars Technica. According to him, it requires a Windows 26H2 installation that has existed for more than ninety days. A fresh installation with updates is therefore not enough. Of the many devices Dormann uses, only one met the conditions.

Microsoft rolls out updates such as 26H2 in phases, so it is unclear how many systems are affected. The company says it has no indications that the vulnerability is being exploited in the wild and that Defender blocks possible attempts. Microsoft has not yet announced a patch.

Administrators can use the winver command to check which version of Windows is running and verify the registry value.