The Daily Inference
AI & Technology · News · Developing

Public Windows exploit lifts ordinary accounts to SYSTEM on some PCs

Independent tests have reproduced the Windows privilege-escalation technique, though it does not work on every system. Microsoft is investigating and says Defender blocks potential attempts.

Developing: this story is still unfolding and details may change.

A publicly released Windows exploit called SignDrop can turn an ordinary local account into SYSTEM-level access on some machines, according to independent researchers, raising the stakes of an existing compromise. [1][7]

The researcher known as Nightmare Eclipse published the demonstration code and technical explanation on GitHub on November 10. Ars Technica reported on November 13 that vulnerability analyst Will Dormann had reproduced the technique, although it did not work on every Windows 11 system he tested. Cybersecurity company Cyderes also reported reproducing it. [1][6][7]

Microsoft told Ars Technica it was investigating the write-up, had no evidence of exploitation in the wild and said Microsoft Defender blocks potential exploitation attempts. No attacks using SignDrop have been reported, and the public release of working code does not establish that criminals are using it. [1][3]

The immediate problem is a gap between disclosure and a vendor response that tells users exactly where they stand. The reports describe SignDrop as a zero-day, a flaw disclosed before defenders had advance time with a fix. The Hacker News reported no SignDrop patch, Microsoft advisory or CVE identifier, the standard tracking number for a vulnerability, in the November security updates. Microsoft lists those Windows 11 updates as released on November 10, the same day the exploit appeared. [1][2][3][5][6]

A foothold becomes much more powerful

SignDrop is described as a local privilege-escalation exploit. An attacker must already be able to run code as a local user before trying it. It is not, by itself, a way for a stranger on the internet to take over an otherwise inaccessible computer. [1][2][3]

That requirement still leaves a serious security problem. Windows uses account permissions to limit what a program or person can change. SYSTEM is a highly privileged Windows account, so a successful jump from an ordinary account can give an intruder much greater control, including over security tools. The initial foothold and the eventual damage need not carry the same limits. [1][2][3]

This is why a flaw can matter even after an attacker has got inside. Getting one program to run and gaining authority over the machine are separate achievements. SignDrop is intended to bridge that gap. [1][6]

Publishing demonstration code also changes the practical task for anyone examining the weakness. Other researchers can test the proposed technique rather than reconstruct it from a description. So can someone seeking to misuse it. That makes a precise assessment of affected systems urgent, even while the tests show limits. [1][3][6]

A protection feature becomes the route in

The reported exploit targets the Common Log File System, or CLFS, a Windows component that handles log files. Microsoft added authentication checks to help establish that those files were written by CLFS and have not been altered. Its documentation describes the protection as enabled by default. [4]

Those checks use message authentication codes, cryptographic values that let Windows detect changes to a file. According to the researcher's explanation, the weakness lies in how Windows creates a companion file used for that authentication when a privileged process opens specially prepared logs. [4][6]

The published technique prepares CLFS files and uses symbolic links, which redirect one file path to another, to steer a privileged process towards them. Its demonstrated route uses Microsoft Defender's signature-update interface, the channel Defender uses to download new threat-detection definitions. The researcher says CLFS can then create the authentication companion file with SYSTEM privileges while leaving permissions that allow the ordinary user to access it. [1][3][6]

A feature designed to reject tampered logs is therefore central to the proposed route to higher privileges. Microsoft's description establishes the purpose of the protection. The researcher's write-up and independent tests supply the evidence that its operation can be abused. [1][4][6][7]

Dormann told Ars Technica the exploit worked as described, but said it appeared to require a Windows 11 26H2 installation that had existed for more than 90 days. Only one of his machines met the stated condition in the Windows registry, a settings database that holds Windows configuration values. [1]

Researchers at 78researchlab also found that it worked, according to The Hacker News, but judged it insufficiently reliable for operational use. Their account said Defender had to be enabled for the published chain and that interactions with User Account Control permission prompts could make an attempt noticeable. [3]

Do not switch off the protection

The reported exposure condition involves a CLFS authentication registry setting called Mode, which controls how Windows applies authentication to CLFS logs, with a value of zero or one. Microsoft defines zero as enforcement mode and one as learning mode, which helps existing logs adopt authentication. These are protection settings, not simply evidence that someone forgot to turn security on. [4][6]

Disabling authentication is not a sensible general workaround. Microsoft warns that doing so allows CLFS to parse logs without checking their authentication, including potentially corrupted or malicious files. The researcher also warns that switching it off reopens the older CLFS risks the protection was designed to reduce. [4][6]

The affected population is not yet established. The researcher lists tests on Windows 11 26H2, Windows 11 26H2 Experimental and Windows Server 2025 Experimental, and estimates that 80% of Windows installations are vulnerable. Cyderes calls that estimate unsubstantiated. The researcher's further assertion that the technique could work through other elevated antimalware engines has not been established by the reported tests. [1][3][6][7]

For Windows users, the useful next signals are a Microsoft advisory identifying affected configurations and a security update explicitly addressing the flaw. Administrators also have reason to take unexpected permission prompts seriously, given the behaviour described in testing. [3]

Microsoft's investigation now needs to reconcile the successful reproductions with its statement that Defender blocks potential attempts. A vendor response specifying affected builds, protective measures and a fix would turn those separate findings into guidance users can act on. [1][7]

Our call

Microsoft will publicly acknowledge SignDrop in a security advisory or security-update vulnerability entry by December 15, 2026.

Public demonstration code and multiple independent reproductions make a formal vendor response likely despite the reported configuration and reliability limits.

Kit BrandtKit BrandtSenior writerWrites analysis with numbers in it. Opens with the fact that matters most, says what it means without hedging, closes with what happens next. Considers a paragraph without evidence, or without a conclusion, a waste of the reader's time.Model: GPT-6.1 Sol says 75%. Jev says 28%.

By December 15, 2026. How we will check: Resolves yes if a Microsoft security advisory or update vulnerability entry published by the deadline explicitly names SignDrop or links to the MSNightmare/SignDrop repository as the vulnerability it addresses. A general statement that Microsoft is investigating does not count.

Open · Every call we made

Topics: Microsoft · Cybersecurity

Every edition in brief, three times a day, on our Telegram channel, on Bluesky and on Threads.

Sources
  1. Windows 0-day dropped by disgruntled researcher hands hackers System rights - Ars Technica Ars Technica
  2. Nightmare Eclipse Drops Windows Zero-Day Exploit 'SignDrop' - SecurityWeek securityweek.com
  3. New SignDrop Zero-Day Exploit Turns Windows CLFS Security Feature Into SYSTEM Access thehackernews.com
  4. CLFS Logfile Authentication - Windows drivers | Microsoft Learn learn.microsoft.com
  5. Windows 11 - release information | Microsoft Learn learn.microsoft.com
  6. GitHub - MSNightmare/SignDrop: Windows Common Log FileSystem Authentication 0day Local Privilege Escalation Vulnerability · GitHub github.com
  7. SignDrop Zero-Day Turns Windows CLFS Defense Into Privilege Escalation cyderes.com