A zero-day vulnerability in Windows 11 26H2 allows BitLocker encryption to be bypassed through Narrator

A zero-day vulnerability in Windows 11 26H2 allows BitLocker encryption to be bypassed through Narrator

A new security flaw affects the lock screen on computers with Windows 11 26H2a version that Microsoft has worked hard to polish. According to a publication in GitHubthis zero-day vulnerability works even with the November patch installed. Therefore, we are facing a known error, but at this time it still lacks an official correction. The researcher behind FastUnlock claims it took five minutes to compromise a BitLocker-encrypted PC.

Remember that BitLocker is the disk encryption system integrated into Windows to protect your data. However, this bug manages to bypass that barrier without having to log in to the computer. In addition, it allows you to run code directly on the computer under a blocking environment account.

What does FastUnlock allow and what requirements does it require?

In practice, the error opens the door to starting external programs without unlocking the user’s session. This way, an attacker can execute code taking advantage of the account WsiAccount. For those who don’t know, this is the account that Windows uses on the lock screen. For example, the researcher points out that you can launch executable files from a USB stick. Likewise, he assures that the behavior was repeated on all the computers where he tested, so it seems generalized.

Of course, exploiting this vulnerability is not possible remotely. This would be the least bad part. And, to take advantage of the failure, the attacker needs to have physical access directly to the locked computer. On the other hand, it also requires a specific condition in the system configuration. At least one of your computer accounts must be linked to a Microsoft online account.

The origin of the failure in Windows Narrator

As the source explains, the problem lies in how the user manages its interface. Windows Narrator. Apparently, by updating its design, Microsoft did not prevent the new interface from being launched from the lock screen. Instead, the old code still maintains the lock that prevents opening that window if it works as SYSTEM. For this reason, the renewed interface operates in the background and allows access to internal system options.

The author had already documented similar Windows lock screen issues before. In fact, he cites as an example a previous ruling known as ZDI-21-1053. However, it has not yet been verified whether Windows 10 It is also vulnerable to this error. For now, Microsoft needs to publish an official patch to correct the problem.