SignDrop: unpatched Windows CLFS zero-day gives local users SYSTEM, public exploit available, no CVE or patch
Matéria consolidada. Reúne 5 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 4 fontes trouxeram em 13/11/2026 00:02; os links antigos trazem para cá.
Fontes: thehackernews.com ↗ bleepingcomputer.com ↗ gbhackers.com ↗ securityonline.info ↗
A researcher known as MSNightmare (aka Chaotic Eclipse, identified by bleepingcomputer.com as Abdelhamid Naceri) disclosed SignDrop, an unpatched local privilege escalation zero-day in the Windows Common Log File System (CLFS) driver (clfs.sys). It lets a standard user obtain NT AUTHORITY\SYSTEM (gbhackers.com). A proof-of-concept exploit and a detailed writeup are public (securityonline.info, thehackernews.com), and the exploit spawns a SYSTEM shell on Windows 11 26H2 and Windows Server builds (securityonline.info). As of 2026-11-12, no CVE or patch has been issued, and Microsoft has neither commented publicly on this issue nor confirmed it (securityonline.info, gbhackers.com, thehackernews.com). No in-the-wild exploitation has been reported (thehackernews.com). The flaw is local-only, so an attacker needs prior code execution, which makes it a likely second-stage step after phishing or malware (gbhackers.com). The flaw abuses the CLFS authentication mitigations Microsoft introduced in October 2025 (bleepingcomputer.com).
Entenda a falha
A vulnerabilidade
SignDrop is an unpatched local privilege escalation in the Windows Common Log File System driver (clfs.sys), in the log-authentication feature Microsoft added in October 2025. A standard user who can already run code gets NT AUTHORITY\SYSTEM. The Hacker News lists Windows 11 25H2, 26H1 and 26H2 and Windows Server 2025; other outlets name only 26H2 and Server 2025 (some say Experimental builds). Systems are exposed when the CLFS Authentication Mode registry value is 0 or 1, and the published chain also needs Defender enabled. No CVE, patch or Microsoft confirmation exists, so there is no fixed version.
Como funciona
A standard user prepares a CLFS log and attaches extra containers with paths the user controls. CLFS writes a companion .cnpf authentication file next to the log, and if an associated container is empty it signs it whether or not a signature file already exists. This is harmless while the user's own process does the work. The exploit then makes a privileged process, in the published code the Defender service via its signature-update call, open the prepared log. Object manager symbolic links redirect the file creation, so the driver creates the .cnpf file as SYSTEM with the original log's permissions, leaving a SYSTEM-created file the user can write, which can be chained into a SYSTEM shell.
Por que é vulnerável
The authentication feature works as designed; the flaw is a logic gap. The .cnpf file is created with the same security attributes as the original log, and the driver creates it in the context of whichever process opens the log, signing empty associated containers without checking for an existing signature. A user-controlled log plus path redirection lets a privileged process create and hand over a file the user can write. The researcher said Microsoft did everything properly but the logic allows abuse. No fix exists, so the articles do not say what one would change.
Onde está
The articles place the flaw in clfs.sys, in how it creates the companion .cnpf authentication file for logs with associated containers (added via the AddLogContainer API); the Defender trigger is the ServerMpUpdateEngineSignature call. No fix commit is named.
Como foi descoberta
The researcher known as MSNightmare (also Chaotic Eclipse; BleepingComputer names Abdelhamid Naceri, a link not confirmed elsewhere) published the exploit and writeup on GitHub on November 10, 2026, the day of Microsoft's November updates. Nothing indicates coordinated disclosure or prior vendor notice; BleepingComputer says he has disclosed earlier zero-days without reporting them privately. He has released many Windows and Defender exploits since April, and Microsoft later fixed some, such as RoguePlanet (CVE-2026-50656) and ShieldBreak (CVE-2026-69414). No in-the-wild attacks are reported and it is not in CISA KEV.
PoC pública
A public proof of concept (C++ source and a Visual Studio project) and writeup are on GitHub. It spawns a SYSTEM shell and was tested by the researcher on Windows 11 26H2, a 26H2 Experimental build and Windows Server 2025 Experimental, with Defender enabled. Sungyup Nam of 78researchlab said colleague Heewon Song found it works but is not reliable enough for operational use. Running it changes every UAC prompt into a standard shell plus a SYSTEM shell, which is noticeable. The claim that it works against any elevated antimalware engine is untested. With no patch, urgency is moderate: check the CLFS Authentication Mode value and watch for a Microsoft advisory.
Explicação gerada por IA a partir da matéria e dos artigos, em 13/11/2026 00:17.
Detalhes técnicos
- The bug abuses the CLFS log-file signing/authentication mechanism, which was meant to block memory-corruption attacks, and turns it into a privilege escalation path (securityonline.info). bleepingcomputer.com ties this to mitigations Microsoft implemented in October 2025.
- The exploit coerces Microsoft Defender into creating an authentication file with SYSTEM privileges. The file inherits attacker-controlled permissions, which yields a SYSTEM shell (gbhackers.com).
- It manipulates the creation of companion ".cnpf" files during privileged log access, using symbolic link path redirection, so the files are created in the security context of a privileged process such as Windows Defender. This produces SYSTEM-level writable files accessible by standard users (thehackernews.com). The root cause is how CLFS handles authentication file creation when a privileged process later accesses the log file (bleepingcomputer.com).
- It may also bypass antivirus and EDR tamper protections, because the file creation appears to come from a trusted security engine (gbhackers.com). bleepingcomputer.com likewise says it can turn the self-defense of AV/EDR engines against them.
- Affected: Windows 11 26H2 and Windows Server 2025 builds. thehackernews.com lists Windows 11 25H2, 26H1 and 26H2 plus Windows Server 2025 with CLFS authentication enabled (mode 0 or 1). About 80% of Windows installations are estimated to be exposed unless specific registry settings disable CLFS authentication enforcement (gbhackers.com, bleepingcomputer.com). That figure is an estimate and appears to trace back to the same underlying disclosure.
- The exploit requires Defender to be enabled. thehackernews.com found it effective in testing but not reliably operational.
- This differs from earlier Defender-related exploits, which relied on Defender file-handling race conditions; SignDrop targets the CLFS authentication mechanism instead (thehackernews.com).
- Detection hints: unexpected ".cnpf" files created by Defender, and ERROR_LOG_METADATA_CORRUPT errors (gbhackers.com).
Remediação
- No official patch exists. Apply the Microsoft fix as soon as one ships, and watch for official Microsoft advisories (thehackernews.com).
- Check the CLFS Authentication registry setting to assess exposure (thehackernews.com, bleepingcomputer.com). The researcher published a PoC for detection (bleepingcomputer.com).
- Enforce least privilege to limit the initial foothold needed (gbhackers.com).
- Monitor for the ".cnpf" file creations by Defender and the ERROR_LOG_METADATA_CORRUPT errors described above (gbhackers.com).
- Do not disable the existing CLFS mitigations. The alternative mitigations expose devices to other memory-corruption exploits (gbhackers.com, bleepingcomputer.com).
- Previous CLFS flaws and mitigations can guide detection until an official fix is available (gbhackers.com).
Relatos divergentes
- Affected systems: securityonline.info (2026-11-11) lists Windows 11 26H2 and "experimental Windows Server builds". gbhackers.com (2026-11-12) names Windows 11 26H2 and Windows Server 2025. bleepingcomputer.com (2026-11-12) says Windows 11 26H2 and Windows Server 2025 Experimental editions. thehackernews.com (2026-11-12, the most specific and recent) lists Windows 11 25H2, 26H1, 26H2 and Windows Server 2025 with CLFS authentication enabled (mode 0 or 1).
- Mechanism: securityonline.info describes abuse of the log-file signing mechanism in general terms. gbhackers.com describes Defender being coerced into creating a SYSTEM-owned authentication file. thehackernews.com adds symbolic link redirection of .cnpf file creation. These descriptions are not necessarily contradictory.
- Researcher identity: gbhackers.com and thehackernews.com name MSNightmare; bleepingcomputer.com names Abdelhamid Naceri. They may refer to the same person, but the link is stated only by the record's alias grouping and not confirmed by a source.
- Microsoft stance: bleepingcomputer.com says Microsoft has warned against malicious exploitation in general but has not addressed this issue; other sources say Microsoft has made no public comment.
- Reliability: thehackernews.com reports the exploit as effective but not reliably operational in testing, while other sources describe it simply as working.
Linha do tempo
-
New SignDrop exploit abuses Windows CLFS driver to escalate local user privileges to SYSTEM
ler a análise desta fonte ocultar
A newly released proof-of-concept exploit named SignDrop leverages a logic flaw in the Windows Common Log File System (CLFS) driver's log authentication feature to escalate a local user to SYSTEM privileges. The exploit manipulates the creation of companion .cnpf files during privileged log access by using symbolic link path redirection, causing files to be created in the security context of a privileged process such as Windows Defender. This creates SYSTEM-level writable files accessible by standard users, enabling privilege escalation. Despite the release of public exploit code and a detailed writeup by researcher MSNightmare, Microsoft has not confirmed the vulnerability, assigned a CVE, or issued a patch as of November 2026 updates. The exploit targets Windows 11 versions 25H2, 26H1, 26H2, and Windows Server 2025 with CLFS authentication enabled (mode 0 or 1). Testing showed the exploit as effective but not reliably operational, and it requires Defender to be enabled. There have been no reported in-the-wild attacks exploiting SignDrop to date. Administrators can assess exposure via the CLFS Authentication registry setting. This vulnerability differs from previous Defender-related exploits by targeting the CLFS driver's authentication mechanism rather than Defender's file handling race conditions. Users should monitor for official advisories and patches from Microsoft.
-
SignDrop Windows zero-day allows privilege escalation to SYSTEM via CLFS authentication flaw
ler a análise desta fonte ocultar
Security researcher Abdelhamid Naceri disclosed a new Windows zero-day vulnerability named SignDrop that enables attackers to gain SYSTEM privileges by abusing mitigations Microsoft implemented in October 2025 for the Common Log File System (CLFS) driver. The vulnerability arises from how CLFS handles authentication file creation when a privileged process later accesses the log file, allowing an attacker to create a file with SYSTEM-level access. This flaw can bypass tamper protection mechanisms of antivirus and endpoint detection and response (EDR) engines, effectively turning their own self-defense against them. The exploit has been tested successfully on Windows 11 26H2 and Windows Server 2025 Experimental editions, with an estimated 80% of Windows installations vulnerable. Currently, there is no patch, and the only mitigation alternatives expose devices to other risks from memory corruption exploits. The researcher published a proof-of-concept (PoC) for detection and recommends checking the relevant registry key to assess vulnerability. Naceri has a history of disclosing Windows zero-days, some of which Microsoft has patched, though others remain unpatched. Microsoft has warned against malicious exploitation but has not yet addressed this particular issue.
-
New Windows SignDrop Zero-Day Elevates Local Users to SYSTEM via CLFS Driver
ler a análise desta fonte ocultar
A new unpatched local privilege escalation zero-day vulnerability called SignDrop has been disclosed by researcher MSNightmare (aka Chaotic Eclipse). The exploit abuses the Common Log File System (CLFS) driver (clfs.sys) on Windows to escalate an attacker from standard user to NT AUTHORITY\SYSTEM by manipulating authentication files created by CLFS logs. The exploit coerces Microsoft Defender to create an authentication file with SYSTEM privileges, inheriting attacker-controlled permissions, enabling a SYSTEM shell. It also potentially bypasses antivirus and EDR tamper protections by masquerading file creation as a trusted security engine’s action. The vulnerability affects Windows 11 26H2 and Windows Server 2025 builds, with an estimated 80% of Windows installations exposed unless specific registry settings disable CLFS authentication enforcement. As this is a local exploit, initial code execution is required, making it suitable as a second-stage privilege escalation after phishing or malware. No CVE or patch has been released yet, and Microsoft has not confirmed the issue or reported in-the-wild exploitation. Defenders are advised to enforce least privilege, monitor unexpected ".cnpf" file creations by Defender, watch for ERROR_LOG_METADATA_CORRUPT errors, and avoid disabling existing CLFS mitigations to prevent re-exposure to other bugs. Previous CLFS flaws and mitigations offer detection guidance until an official fix is available.
-
SignDrop Windows CLFS zero-day allows privilege escalation, exploit public
ler a análise desta fonte ocultar
A researcher known as MSNightmare disclosed a zero-day vulnerability in Windows CLFS that enables a standard user to gain SYSTEM privileges. This flaw exploits the log-file signing mechanism, which was intended to prevent memory corruption attacks, but is abused to turn the feature into a local privilege escalation path. The proof-of-concept exploit is now publicly available on GitHub, demonstrating how to spawn a SYSTEM shell on Windows 11 26H2 and experimental Windows Server builds. No patch has been issued yet, and no attacks are reported in the wild. Microsoft has not publicly commented.