Skip to content
Annuaire
Sections
Cybersecurity

SignDrop: an unpatched Windows zero-day grants SYSTEM rights via CLFS

L’essentiel

SignDrop, code released on 10 November, hijacks Windows' CLFS protection to obtain SYSTEM rights. No patch yet: who is exposed and what to do.

À retenir

SignDrop, code released on 10 November, hijacks Windows' CLFS protection to obtain SYSTEM rights. No patch yet: who is exposed and what to do.

On 10 November 2026, Patch Tuesday, a researcher released attack code dubbed SignDrop that allows an ordinary Windows user to obtain SYSTEM rights. The flaw hijacks a protection that Microsoft added to the CLFS logging system at the end of 2025. As of 17 November 2026, the security updates published by Microsoft contained neither a CVE identifier nor a fix for this flaw, and the code works according to researchers who have tested it.

An anti-exploit protection turned against Windows

CLFS, short for Common Log File System, is a Windows kernel logging service provided by the clfs.sys driver. It has long been a prime target: the Howler Cell team at Cyderes points out, citing a Microsoft blog post from August 2024, that 19 of the 24 CLFS vulnerabilities recorded over five years stemmed from insufficient validation of log data structures, the category Microsoft wanted to block. To do so, the company introduced, with the updates of 28 October 2025, an authentication mechanism that signs logs with an HMAC code, stored in a file with the .cnpf extension.

It is precisely this mechanism that SignDrop exploits. As IT-Connect explains in detail, the attack first creates a CLFS log with a standard account, then gets Microsoft Defender, which runs with the highest privileges, to open it. The missing .cnpf file is then generated with SYSTEM rights, but it retains permissions that an ordinary user can modify. Using object manager symbolic links, the attacker redirects this creation to a location of their choice: in the demonstration, an hid.dll library placed in a Windows folder. The attacker replaces its contents, triggers a User Account Control prompt, and the consent.exe program, running as SYSTEM, loads the booby-trapped library.

No memory corruption is involved. The author admits it himself, quoted by IT-Connect: “Everything is done correctly by Microsoft here, but the logic allows abuse.” The flaw comes from the sequence of legitimate operations, not from a classic programming error.

A researcher who publishes without waiting for Microsoft

The code is signed by Abdelhamid Naceri, a former Microsoft employee who publishes under the pseudonyms Nightmare Eclipse or MSNightmare. Cyderes, which links these pseudonyms to one and the same person, counts sixteen public disclosures of vulnerabilities unknown to the vendor between 3 April and 10 November 2026, or roughly one every fourteen days, SignDrop being the sixteenth. IT-Connect places his previous episode targeting Windows in September, with BigDiskBuster, which blocked Defender updates.

Independent tests confirm the essentials. Howler Cell says it reproduced the attack from a standard session and obtained a console with SYSTEM rights, without any visible prompt, and assesses with high confidence that the public code achieves this result when CLFS authentication is active. The German site Borncity, on the other hand, reports the view of a researcher at 78researchlab, Heewon Song, who believes the exploit works in principle but lacks reliability for targeted operations. Borncity also stresses that Defender must be active on the targeted machine.

Who is exposed, and what remains uncertain

According to IT-Connect, the targeted mechanism arrived with the Windows 11 25H2 and Windows Server 2025 updates released from October 2025 onwards: the machines on which it is active are the ones within scope. The researcher says he tested Windows 11 26H2 and preview builds of Windows Server 2025. He claims that 80% of installations are vulnerable, but Cyderes describes this figure as unsubstantiated and gives it low confidence. His claim that the technique also defeats other antivirus and detection tools remains to be verified.

It is important to keep things in proportion: SignDrop is a local privilege escalation. The attacker must already be able to run code on the machine, for example after a successful phishing attack. This type of flaw is then used to turn limited access into full control, a classic step before deploying ransomware. According to Cyderes and Borncity, no real-world attack had been reported as of their publication date. Microsoft had not responded publicly as of 11 November. As of 17 November, Microsoft’s November security updates, last revised on 16 November, still contained no entry for CLFS.

What to do while waiting for a fix

  • Measure exposure: IT-Connect indicates that the state of the mechanism can be read from the Mode value of CLFS\Authentication, under HKLM\SYSTEM\CurrentControlSet\Services. Values 0 (enforcement) and 1 (learning) fall within SignDrop’s scope. Cyderes points out that this value alone does not guarantee that the attack will succeed.
  • Do not disable CLFS protection: both sources agree that this would reopen the door to older vulnerabilities, including CVE-2025-29824, already exploited by ransomware groups.
  • Limit the execution of unapproved code with application and script control rules, as Cyderes advises.
  • Watch for signs of the attack: the appearance of an hid.dll file in the Windows “ink” folder, where it does not originally exist; consent.exe loading libraries from that location; and Defender signature update calls launched outside its service. The code deletes the library after use, so file creation telemetry must be retained.

The next Patch Tuesday, scheduled for 8 December 2026, will show whether Microsoft fixes the problem. Until then, security teams would be best served by hardening initial access, since that is what SignDrop depends on.

Frequently asked questions

Can SignDrop be used to hack a PC remotely?

No. It is a local privilege escalation: the attacker must already have access to the machine with a standard account. The flaw is used to move from this limited account to SYSTEM rights, the highest in Windows.

Has Microsoft released a fix for SignDrop?

No, not as of 17 November 2026: the November security updates, revised on 16 November, contained no CLFS entry, and the analyses published on 12 and 13 November reported no CVE identifier, advisory or fix.

Should CLFS authentication be disabled for protection?

No. IT-Connect and Cyderes advise against it: disabling it would once again expose machines to older vulnerabilities, already exploited by ransomware groups. It is better to check the registry value, strengthen application control and monitor the indicators.

Sources

Sur votre appareil

Comprendre cet article

L’analyse utilise l’intelligence locale du navigateur lorsqu’elle existe, sinon un résumé extractif. Le texte n’est envoyé à aucun service extérieur.

Facebook X LinkedIn

Ensuite A lire aussi

Free, no spam, one-click unsubscribe.