Skip to main content

“SignDrop” Windows Zero-Day Grants SYSTEM Access With No Patch Available

Scope: Windows 11 26H2 and Windows Server 2025, with broader exposure claimed by the researcher; no CVE assigned, no patch exists**

Severity: Amber

Researcher Abdelhamid Naceri, publishing under the handle MSNightmare, released a working proof-of-concept exploit called SignDrop on GitHub on November 10, 2026, with no coordinated disclosure to Microsoft beforehand. The exploit targets clfs.sys, the kernel driver behind Windows’s Common Log File System, specifically abusing an authentication mitigation Microsoft itself introduced in October 2025 to prevent a different class of CLFS attacks. SignDrop turns that protective signing mechanism against itself: a high-privilege process, in the published proof-of-concept Windows Defender’s antimalware service, can be manipulated into creating a file in a protected location, and the new file inherits permissions that give a standard, unprivileged local user write access to something SYSTEM created, which the exploit then chains into a full SYSTEM-level shell. This is a local privilege escalation primitive, meaning an attacker needs some form of initial code execution as a normal user first, but once that foothold exists, SignDrop provides a path to complete system compromise and the ability to blind security tooling. The researcher reports testing against Windows 11 26H2 and Windows Server 2025 builds, and claims broader exposure across systems with either of CLFS authentication’s two active modes. As of this writing, Microsoft has not issued a CVE identifier, security advisory, or patch, and the flaw is not yet in CISA’s exploited vulnerabilities catalog, though no patch existing does not mean no risk, particularly given the proof-of-concept is already public. Organisations should check their CLFS authentication mode via the registry value at HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication, and should not disable CLFS authentication entirely as a workaround, since that reintroduces the older vulnerability class the feature was built to close; instead, tighten who can execute code on important systems and monitor for unusual file creation activity by Defender or other high-privilege processes.

The Uganda National CERT and Coordination Center (CERT.UG/CC) encourages users and administrators to review the recommendations and apply the necessary updates.