CVE-2025-26637: BitLocker Security Feature Bypass Vulnerability
First published: Tue Apr 08 2025(Updated: )
<p>Protection mechanism failure in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack.</p>
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft Windows Server 2022 23H2 | ||
| Windows 10 | =22H2 | |
| Windows 11 | =24H2 | |
| Windows 11 | =22H2 | |
| Microsoft Windows Server 2022 | ||
| Microsoft Windows Server 2019 | ||
| Microsoft Windows Server 2025 | ||
| Microsoft Windows Server 2016 | ||
| Windows 10 | =22H2 | |
| Windows 10 | =1607 | |
| Microsoft Windows Server 2025 | ||
| Windows 11 | =23H2 | |
| Microsoft Windows Server 2012 R2 | ||
| Windows 11 | =22H2 | |
| Microsoft Windows Server 2022 | ||
| Windows 10 | =21H2 | |
| Microsoft Windows Server 2012 R2 | ||
| Microsoft Windows Server 2019 | ||
| Windows 10 | =1809 | |
| Windows 11 | =23H2 | |
| Windows 10 | =21H2 | |
| Microsoft Windows Server 2016 | ||
| Windows 11 | =24H2 | |
| Windows 10 | =22H2 | |
| Windows 10 | =1607 | |
| Windows 10 | =21H2 | |
| Windows 10 | =1809 | |
| Windows 10 | ||
| Windows 10 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-26637?
CVE-2025-26637 has a critical severity rating due to its potential to allow unauthorized access to sensitive data.
How do I fix CVE-2025-26637?
To fix CVE-2025-26637, apply the latest security updates provided by Microsoft for the affected Windows products.
Which versions of Windows are affected by CVE-2025-26637?
CVE-2025-26637 affects multiple versions of Windows, including Windows 10, Windows 11, and Windows Server 2022.
What are the potential impacts of CVE-2025-26637?
An attacker exploiting CVE-2025-26637 can bypass BitLocker security, potentially gaining unauthorized access to encrypted data.
Is there a workaround for CVE-2025-26637?
As of now, Microsoft recommends applying the security patches as the primary solution and has not listed alternate workarounds for CVE-2025-26637.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/type
- agent/references
- collector/msrc-cve
- source/Microsoft
- agent/software-canonical-lookup
- agent/first-publish-date
- agent/softwarecombine
- collector/msrc
- collector/nvd-api
- source/NVD
- agent/author
- agent/weakness
- agent/last-modified-date
- agent/severity
- agent/source
- agent/description
- agent/tags
- agent/event
- vendor/microsoft
- canonical/microsoft windows server 2022 23h2
- canonical/windows 10
- version/windows 10/22h2
- canonical/windows 11
- version/windows 11/24h2
- version/windows 11/22h2
- canonical/microsoft windows server 2022
- canonical/microsoft windows server 2019
- canonical/microsoft windows server 2025
- canonical/microsoft windows server 2016
- version/windows 10/1607
- version/windows 11/23h2
- canonical/microsoft windows server 2012 r2
- version/windows 10/21h2
- version/windows 10/1809