Encrypted-drive access via undisclosed physical bypass
Published Sep 15, 2021 · Updated Aug 10, 2026
BitLocker bypass in affected Windows releases allows physically proximate attackers to access encrypted system-drive data. Microsoft identifies the locus only as BitLocker Device Encryption on the system storage device and has not disclosed the faulty operation. Exploitation requires physical access to a powered-off system; the bounded consequence is unauthorized access to encrypted data.
Summary
What happened
BitLocker bypass in affected Windows releases allows physically proximate attackers to access encrypted system-drive data. Microsoft identifies the locus only as BitLocker Device Encryption on the system storage device and has not disclosed the faulty operation. Exploitation requires physical access to a powered-off system; the bounded consequence is unauthorized access to encrypted data.
The record
- CVE
- CVE-2021-38632
- Published
- Sep 15, 2021
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- T1006
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2021CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.17763.0 <10.0.17763.2183
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo