BitUnlocker Attack Bypasses BitLocker on Windows 11 in Under 5 Minutes

Overview

A newly disclosed tool named BitUnlocker demonstrates a practical downgrade attack against Microsoft’s BitLocker full-disk encryption on Windows 11 systems.

The attack exploits a gap between Microsoft's July 2025 security patches and the continued trust of older Secure Boot signing certificates, enabling attackers with physical access to boot vulnerable Windows components and gain access to encrypted disks.

The technique is based on CVE-2025-48804, one of four critical Windows zero-day vulnerabilities patched during Microsoft’s July 2025 Patch Tuesday release.

According to security researchers at Intrinsec, the vulnerability impacts the Windows Recovery Environment (WinRE) and specifically abuses the System Deployment Image (SDI) loading mechanism.

How the Attack Works

The vulnerability exists in the way the Windows boot manager processes SDI files and WIM (Windows Imaging Format) images during recovery boot operations.

SDI and WIM Manipulation

During boot:

  1. The Windows boot manager loads a legitimate WIM image referenced by an SDI file.
  2. Integrity checks are performed only on the first legitimate WIM.
  3. A second attacker-controlled WIM can be appended to the SDI blob table.
  4. The boot manager ultimately boots from the malicious WIM instead of the verified one.

The malicious WinRE image is modified to launch:

cmd.exe

with the BitLocker-protected volume already decrypted and mounted.

This gives attackers direct access to the filesystem with full administrative privileges.

Why Secure Boot Fails to Stop It

Microsoft released a patched bootmgfw.efi boot manager in July 2025. However, the patch alone does not fully mitigate the issue.

The core weakness lies in the continued trust of the legacy:

  • Microsoft Windows PCA 2011 signing certificate

Secure Boot validates the signing certificate of a binary rather than its version number.

As a result:

  • Older vulnerable boot managers signed with PCA 2011 remain trusted
  • Secure Boot accepts them as legitimate
  • TPM measurements remain valid
  • BitLocker automatically releases the Volume Master Key (VMK)

Unless systems were freshly installed after early 2026 or migrated to newer certificate chains, most Windows devices still trust PCA 2011.

Attack Requirements

Researchers state the attack requires only:

  • Physical access to the target system
  • A USB drive or PXE boot server
  • No specialized hardware

The attacker boots the machine using:

  • A vulnerable pre-patch bootmgfw.efi
  • A modified BCD configuration
  • A tampered SDI file containing a malicious WinRE image

Because the vulnerable boot manager is still trusted by Secure Boot, the attack proceeds without warnings.

Affected Systems

The attack impacts systems configured with:

  • TPM-only BitLocker protection
  • Secure Boot databases still trusting PCA 2011

Potentially vulnerable environments include many enterprise Windows 11 deployments that:

  • Installed patches without certificate migration
  • Continue using legacy Secure Boot trust chains

Protected Configurations

Researchers confirmed the following setups are protected:

TPM + PIN BitLocker

Systems using:

  • TPM + PIN pre-boot authentication

remain protected because the TPM will not release the VMK without user interaction.

CA 2023 Migration

Systems that completed the:

  • KB5025885 migration

and moved boot manager signing to:

  • Windows UEFI CA 2023

are also protected from the downgrade attack.

Mitigation Recommendations

Security teams are advised to implement the following mitigations immediately.

1. Enable TPM + PIN

The most effective protection is enabling:

  • TPM + PIN pre-boot authentication

This prevents automatic VMK release during manipulated boot sequences.

2. Deploy KB5025885

Microsoft’s KB5025885 update:

  • Migrates boot manager signing to CA 2023
  • Introduces revocation protections
  • Eliminates the downgrade path

3. Verify Boot Manager Signatures

Administrators should verify the active bootmgfw.efi binary is signed using:

  • Windows UEFI CA 2023

instead of the older PCA 2011 certificate.

Tools such as:

sigcheck

can be used for validation.

4. Reduce WinRE Exposure

For high-security systems where TPM + PIN cannot be enforced:

  • Remove or restrict the WinRE recovery partition

to minimize exposure to this attack class.

Public PoC Raises Risk

Researchers have publicly released a working proof-of-concept on GitHub, significantly increasing the likelihood of real-world abuse.

The attack’s low hardware requirements and rapid execution time make it especially dangerous for:

  • Enterprise laptops
  • Stolen devices
  • Insider threat scenarios
  • Border crossing device seizures
  • Targeted intrusion operations

Conclusion

BitUnlocker highlights a critical weakness in the Windows Secure Boot ecosystem: patched components remain exploitable when legacy trusted certificates are still accepted.

The attack demonstrates how downgrade techniques can bypass BitLocker protections even on fully patched Windows 11 systems, provided organizations have not completed certificate migration and revocation procedures.

Enterprises relying solely on TPM-only BitLocker should prioritize:

  • TPM + PIN deployment
  • CA 2023 migration
  • Secure Boot trust auditing

before attackers begin operationalizing BitUnlocker in broader campaigns.