If your staff carry Windows laptops, a newly reported zero-day raises a fair question about how far a locked screen can be trusted. Someone with brief physical access and a keyboard may be able to run software as the signed-in user, and if the report holds, BitLocker would not keep the files protected. The claim is fresh and lightly tested, so treat it as a serious report, not a confirmed fact.

What happened

According to Tom’s Hardware, the bug was discovered by Abdelhamid Naceri, known as Nightmare Eclipse, a Windows researcher credited with about a dozen zero-day findings in Microsoft’s operating system. It affects Windows 11 and possibly Windows 10. An attacker can partly bypass the lock screen and run software as the logged-in user, and seemingly reach that person’s data.

The method needs only a keyboard. On the lock screen, the attacker chooses the “Forgot my PIN” option and presses Win+U to start Narrator. The Narrator window stays hidden behind the lock screen, but holding Caps Lock lets the attacker steer it with the arrow keys and Enter. After a short trip through Narrator, the attacker lands in Settings.

From Settings there are several routes. One is to set Autoplay under Bluetooth and Devices so a USB stick’s contents appear, then plug in a drive carrying the attacker’s own software. Another applies to personal machines, where the user normally holds administrator rights, so the attacker can create a new account.

Naceri says the flaw seems “extremely consistent in every machine I tested it in.” A Reddit sysadmin quoted by Tom’s Hardware says it worked on the Intune-enrolled devices they manage, and that they could launch anything in the context of the logged-in user. They also reported being able to move invisibly through programs the user had open before locking. Beyond these accounts, little independent testing exists yet.

Why it matters

Physical access is exactly the scenario that lock screens and BitLocker are meant to cover. The source hedges on this point, saying the bug “seemingly” exposes user data and that BitLocker would fail to protect files only “if true.” It does not explain why encryption would not help.

One possible reading, and this is our own speculation, is that the weakness sits in the lock screen as a barrier and not in the encryption itself. Nothing in the reporting confirms that, so do not build policy on it.

The report also challenges a common assumption in security policy: that full-disk encryption plus a lock screen covers a lost or stolen laptop. The sysadmin Tom’s Hardware spoke to says the Windows lock screen has always felt like a kludge and expects further hacks. That is one person’s opinion, but it is worth noting alongside a researcher with a long record of Windows findings.

What it means for you

None of the steps below is a confirmed fix. They are precautions that follow from how the attack is described:

  • Test your own fleet. Have IT try the reported sequence on a managed test device, including Intune-enrolled ones, and record the result before you set policy.
  • Reduce local admin rights. The reported account-creation path depends on the user being an administrator. Standard-user accounts may narrow what an intruder can do.
  • Review USB and Autoplay controls. If your management tooling can restrict removable storage, check that it holds in this scenario.
  • Be cautious with unattended laptops. As a general precaution, ask staff not to leave devices unattended in shared or public spaces. We have no evidence that shutting a machine down defeats this attack.
  • Ask Microsoft and your reseller. Request any guidance on the issue and ask whether your endpoint security product detects the behavior.

Update your lost-device playbook as well. If a laptop vanishes, consider whether anything open or signed in on it needs its credentials and sessions rotated.

What to watch

  • Whether Microsoft acknowledges the flaw and offers a patch or a workaround.
  • Independent testing that confirms or narrows the claim, including whether Windows 10 and non-Intune machines are affected.
  • Further lock screen bypasses from the same researcher or others.

Sources