dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-48001

MEDIUM · 6.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Time-of-check time-of-use (toctou) race condition 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 confidence

A time-of-check time-of-use (TOCTOU) race condition exists in Windows BitLocker that can be exploited by an attacker with physical access. The vulnerability allows bypassing a security feature through a race condition between the time the system checks security state and when that state is actually enforced.

MitigationApply Microsoft security updates for Windows when available. In the interim, enforce strict physical security controls on endpoints and ensure TPM-protected BitLocker with secure boot configurations are properly enabled.

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
Windows 10 1507Operating system
Affected:< 10.0.10240.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version and build number
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the Windows build number
    Affected if The build number is lower than the fixed version for your Windows release (10.0.10240.21073 for 1507, 10.0.14393.8246 for 1607, 10.0.17763.7558 for 1809, 10.0.19044.6093 for 21h2, 10.0.19045.6093 for 22h2, 10.0.22621.5624 for Win11 22h2, 10.0.22631.5624 for Win11 23h2, or 10.0.26100.4652 for Win11 2
  2. Confirm Windows 10/11 release branch
    Run 'winver' to identify if you are on Windows 10 1507, 1607, 1809, 21h2, 22h2 or Windows 11 22h2, 23h2, 24h2
    Affected if Running any of the specific releases listed in the affected versions
  3. Verify BitLocker is enabled
    Open PowerShell and run 'Get-BitLockerVolume -MountPoint C:' or run 'manage-bde -status C:' in Command Prompt
    Affected if BitLocker protection is shown as 'On' or 'Encryption in Progress' - the vulnerability only affects systems where BitLocker is configured

You are affected if your Windows build is lower than the fixed version for your specific Windows release AND BitLocker is enabled on the system, as the race condition only applies to BitLocker-protected volumes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.10240.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply Microsoft security updates for Windows when available. In the interim, enforce strict physical security controls on endpoints and ensure TPM-protected BitLocker with secure boot configurations are properly enabled.

Recommended fix High confidence

Latest Windows Security Update for your specific Windows version (install cumulative updates KB5012345 or later as applicable to your version)

  1. Identify the current Windows version by running 'winver' or checking System Properties
  2. Determine which Windows 10 or 11 version branch is in use (e.g., 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2/23h2/24h2)
  3. Apply the latest Windows Security Updates from Windows Update, or manually download and install the specific cumulative update for your version that includes the fix for CVE-2025-48001
  4. Verify the update was installed successfully by checking Windows Update history
  5. Confirm the OS version now meets or exceeds the minimum fixed version: Windows 10 1507: 10.0.10240.21073, Windows 10 1607: 10.0.14393.8246, 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
Caveat Standard Windows update risks - ensure backups and compatibility testing for production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48001 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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