4-Hour BitLocker Zero-Day Cracks Windows SYSTEM Shell

If BitLocker can be bypassed after a Microsoft Defender Offline Scan, what else in Windows Recovery Mode is being trusted too much?

That is the real question raised by GreatXML, a newly published exploit from security researcher Chaotic Eclipse, also known as Nightmare Eclipse, according to Security Affairs. The exploit reportedly bypasses BitLocker and opens a command shell with full SYSTEM privileges while Windows is in Recovery Mode.

There is no patch yet, per the source, a risk pattern also seen in the PeopleSoft zero-day. That matters because defenders cannot treat this as a normal “wait for Windows Update” problem. Any machine that previously ran a Defender offline scan may have the artifacts GreatXML needs.

Why does a Defender offline scan change the BitLocker threat model?

Microsoft Defender Offline Scan is supposed to help when malware cannot be removed while Windows is running. The system reboots into Windows Recovery Environment, or WinRE, and scans before the full operating system loads.

GreatXML appears to turn that recovery path into an attack path.

Security Affairs reports that Defender’s offline scan feature leaves configuration artifacts on the recovery partition. GreatXML abuses the way WinRE processes XML files during boot. The result, according to the published proof-of-concept description, is a shell with unrestricted access to the BitLocker-protected volume.

“If defender offline scan was initiated in the victim machine at any point then there is no need to login, the machine is automatically vulnerable.”

That sentence is the core of the risk. The issue is not that BitLocker’s encryption has been mathematically broken. The reported weakness sits around BitLocker, in the boot and recovery workflow that decides what happens before normal Windows controls are fully in play.

That distinction matters. BitLocker can still be the right control. But GreatXML shows that encryption is only as strong as the recovery process around it.

What exactly did Chaotic Eclipse publish with GreatXML?

On June 10, Chaotic Eclipse published a working exploit called GreatXML. It came one day after RoguePlanet, another exploit targeting Microsoft Defender that Security Affairs says can lead to local privilege escalation.

The researcher framed GreatXML as a fast find, not a long campaign of cryptographic research.

“This was an accidental discovery, it took a total of 4 hours to find this. If you ever attempted to use Windows Defender Offline Scan, you’re automatically vulnerable to a bitlocker bypass.”

That “4 hours” claim is unsettling for a different reason than the bypass itself. XOOMAR analysis: if accurate, it suggests a brittle edge case in how Windows recovery and security tooling interact. This is not a brute-force defeat of drive encryption. It is a failure in the surrounding trust chain.

Public exploit details also compress the defender timeline. Attackers do not need to wait for Microsoft to reproduce, triage, patch, and ship a fix before they begin testing the technique.

For readers tracking the wider run of Windows privilege and recovery issues, XOOMAR has covered adjacent security pressure in Windows Zero-Days Let Patched PCs Hand Over SYSTEM and the operational patching burden in 208 CVEs Turn Microsoft Patch Tuesday Into a Fire Drill.

Who should assume exposure after running Defender Offline Scan?

Systems that have run Defender Offline Scan and still retain the relevant recovery artifacts should be treated as potentially exposed until Microsoft or trusted researchers provide clearer guidance.

The source describes one important condition: the exploit path is easier if Defender Offline Scan has already been used. If it has not, the researcher said an attacker may need to log in and initiate the scan or find another way to boot into the required recovery state. The researcher also said they had not fully investigated every possible trigger path.

That leaves defenders with an uncomfortable triage problem.

The highest concern is not every Windows PC on the internet. It is machines where physical access, stolen hardware, shared access, or local control is plausible.

That includes enterprise laptops, shared workstations, incident response machines, and high-value endpoints that have used Defender Offline Scan. BitLocker still reduces risk, but GreatXML makes the recovery partition and boot path part of the security boundary.

How would a stolen BitLocker laptop change under GreatXML?

Take a simple case. An employee’s BitLocker-protected laptop is stolen from a car. The company assumes the data is safe because the thief does not know the Windows password.

Before GreatXML, that assumption would often center on whether BitLocker was enabled and whether the recovery key was protected. After GreatXML, defenders need one more question: did this machine ever run Defender Offline Scan?

If yes, and if the relevant artifacts remain, Security Affairs reports that GreatXML can open a SYSTEM shell in Recovery Mode with unrestricted access to the BitLocker volume. That makes the local contents of the device the immediate concern.

XOOMAR analysis: claims about broader compromise, such as identity abuse or access to internal tools, depend on how the endpoint was configured and what was stored locally. The supplied source does not prove those follow-on outcomes. The grounded risk is narrower but still serious: a locked encrypted device may no longer behave like a locked encrypted device under the reported conditions.

The lesson is not “turn off BitLocker.” It is that device encryption cannot carry the whole burden alone. Recovery settings, boot controls, endpoint inventory, and rapid response after device loss all matter.

What can IT teams do before Microsoft ships a GreatXML fix?

There is no patch listed in the source material. That means the immediate job is containment, not closure.

Start with exposure mapping.

• Inventory: Identify endpoints that have run Microsoft Defender Offline Scan, especially laptops and shared machines.
• Priority: Focus first on mobile devices, high-value users, and systems where physical access is realistic.
• Recovery review: Check BitLocker recovery settings and recovery partition handling under existing policy.
• Boot controls: Validate Secure Boot configuration and restrict unnecessary recovery or boot options where policy allows.
• Device loss response: If a missing device previously ran an offline scan, do not rely on “BitLocker enabled” as the only safety signal.
• Monitoring: Watch for unusual Recovery Mode or boot environment activity where telemetry supports it.

Microsoft’s Security Response Center has already criticized the broader zero-day dumps tied to this disclosure wave.

“The details of these vulnerabilities were not shared with Microsoft prior to release, and the disclosures put our customers at unnecessary risk.”

That statement was about recent public disclosures including RedSun, UnDefend, BlueHammer, YellowKey, GreenPlasma, and MiniPlasma, not just GreatXML. Security Affairs also notes that GreatXML follows earlier Chaotic Eclipse disclosures affecting Defender, BitLocker, and Windows components.

The practical watch item now is narrow but urgent: whether Microsoft confirms the GreatXML behavior, publishes mitigation guidance, or ships a fix for the WinRE and Defender Offline Scan interaction. Until then, affected Windows systems should be treated as facing a practical local attack risk, not a lab curiosity.

Impact Analysis

• The reported exploit targets Windows Recovery Mode workflows rather than breaking BitLocker encryption directly.
• Systems that previously ran Microsoft Defender Offline Scan may be exposed if recovery partition artifacts remain present.
• With no patch available yet, defenders may need to review WinRE and offline scan usage instead of waiting for a standard update.