Physical security bypass via unpatchable ROM code
Published Oct 14, 2025 · Updated Oct 14, 2025
Security bypass in Microsoft Windows BitLocker allows physically proximate attackers to access encrypted data through an affected device. Microsoft identifies an inability to patch ROM code but has not published the ROM component, vulnerable routine, or physical input that reaches it. Physical possession is required; successful exploitation bypasses BitLocker protections and exposes protected data, while availability impact is not reported.
Summary
What happened
Security bypass in Microsoft Windows BitLocker allows physically proximate attackers to access encrypted data through an affected device. Microsoft identifies an inability to patch ROM code but has not published the ROM component, vulnerable routine, or physical input that reaches it. Physical possession is required; successful exploitation bypasses BitLocker protections and exposes protected data, while availability impact is not reported.
The record
- CVE
- CVE-2025-55338
- Published
- Oct 14, 2025
- Updated
- Oct 14, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-1310, CWE-288, CAPEC-682
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 2025Record 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.21161
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