Physical drive-protection bypass via undisclosed mechanism
Published Jul 8, 2025 · Updated Feb 13, 2026
Protection mechanism failure in Microsoft Windows BitLocker allows physically proximate attackers to bypass drive protection. Microsoft has not published which BitLocker component or protection check fails, nor the wrong operation it performs on attacker-controlled input. Physical access to a BitLocker-protected device is required, and successful exploitation defeats the protection intended to prevent unauthorized access to its data.
Summary
What happened
Protection mechanism failure in Microsoft Windows BitLocker allows physically proximate attackers to bypass drive protection. Microsoft has not published which BitLocker component or protection check fails, nor the wrong operation it performs on attacker-controlled input. Physical access to a BitLocker-protected device is required, and successful exploitation defeats the protection intended to prevent unauthorized access to its data.
The record
- CVE
- CVE-2025-48800
- Published
- Jul 8, 2025
- Updated
- Feb 13, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-693
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Feb 13, 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.21073
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