Physical protection bypass via undisclosed mechanism
Published Apr 8, 2025 · Updated Aug 10, 2026
Protection mechanism failure in Microsoft Windows BitLocker allows physically proximate attackers to bypass drive-encryption protections. Microsoft has not disclosed the affected BitLocker locus or the operation that fails to enforce protection. Exploitation requires physical access to an affected device and can compromise protected data confidentiality, integrity, and availability.
Summary
What happened
Protection mechanism failure in Microsoft Windows BitLocker allows physically proximate attackers to bypass drive-encryption protections. Microsoft has not disclosed the affected BitLocker locus or the operation that fails to enforce protection. Exploitation requires physical access to an affected device and can compromise protected data confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-26637
- Published
- Apr 8, 2025
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-693
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2025CVE 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.10240.0 <10.0.10240.20978
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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