CVE-2025-48003
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedProtection mechanism failure in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCVE-2025-48003 is a protection mechanism failure vulnerability in Windows BitLocker that allows an unauthorized attacker to bypass a security feature via a physical attack. The vulnerability enables circumvention of BitLocker's encryption protection when an attacker has physical access to the affected system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.17763.7558< 10.0.19044.6093< 10.0.19045.6093< 10.0.22621.5624< 10.0.22631.5624< 10.0.26100.4652< 10.0.17763.7558< 10.0.20348.3932CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows version and build numberOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the exact build number. Compare this to the affected version ranges listed in the CVE.Affected if The installed Windows version build number is lower than the fixed version for your specific Windows release (e.g., Windows 10 1809 build < 17763.7558, Windows 11 22h2 build < 22621.5624, etc.)
-
Verify BitLocker is enabledOpen an elevated Command Prompt and run 'manage-bde -status' or use PowerShell with 'Get-BitLockerVolume' to see if BitLocker encryption is active on any drives.Affected if BitLocker is not enabled on the system drives, as the vulnerability only affects systems where BitLocker protection is in use.
-
Check BitLocker protection statusRun 'manage-bde -status C:' or use PowerShell 'Get-BitLockerVolume -MountPoint C:' to see whether protection is 'On', 'Paused', or 'Off'.Affected if BitLocker protection status shows 'Paused' or 'Off', indicating the volume is not actively protected.
-
Confirm TPM protector statusRun 'manage-bde -status C:' and look for the 'Key Protectors' section, or use PowerShell 'Get-BitLockerVolume | Select-Object -ExpandProperty ProtectionStatus' to verify TPM is configured as a key protector.Affected if TPM-based protection is not configured as a key protector, as the bypass relates to physical attack scenarios against TPM-protected systems.
A system is affected if it runs a Windows version with a build number lower than the fixed version AND has BitLocker enabled with TPM protection, as the vulnerability enables physical attack bypass of BitLocker encryption.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.17763.755810.0.19044.609310.0.19045.6093
Organizations should implement additional physical security controls and monitor for unauthorized physical access attempts. Review BitLocker configuration and ensure TPM protection is properly enabled and configured.
Windows 10 1809: 10.0.17763.7558+ | Windows 10 21h2: 10.0.19044.6093+ | Windows 10 22h2: 10.0.19045.6093+ | Windows 11 22h2: 10.0.22621.5624+ | Windows 11 23h2: 10.0.22631.5624+ | Windows 11 24h2: 10.0.26100.4652+ | Windows Server 2019: 10.0.17763.7558+ | Windows Server 2022: 10.0.20348.3932+
- Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Determine if your current version is below the fixed threshold for your Windows release
- Apply the appropriate Windows security update for your version: For Windows 10 1809/Windows Server 2019, upgrade to 10.0.17763.7558 or later; For Windows 10 21h2, upgrade to 10.0.19044.6093 or later; For Windows 10 22h2, upgrade to 10.0.19045.6093 or later; For Windows 11 22h2, upgrade to 10.0.22621.5624 or later; For Windows 11 23h2, upgrade to 10.0.22631.5624 or later; For Windows 11 24h2, upgra
- Install the update via Windows Update, WSUS, or by downloading the update from the Microsoft Update Catalog
- Restart the system as required by the update
- Verify the installed version matches or exceeds the fixed version for your Windows release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48003 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48003 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data