dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-26637

MEDIUM · 6.8 CVSS v3.1 Developing Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 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
Protection 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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-30.

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.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775
Windows Server 2012Operating system
Affected:= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7969

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

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.20978 / 10.0.14393.7969 / 10.0.19045.5737 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.19045.5737
Recommended fix High confidence

Windows 10 1507: 10.0.10240.20978+ | Windows 10 1607: 10.0.14393.7969+ | Windows 10 22h2: 10.0.19045.5737+ | Windows 11 22h2: 10.0.22621.5189+ | Windows 11 23h2: 10.0.22631.5189+ | Windows 11 24h2: 10.0.26100.3775+ | Windows Server 2016: 10.0.14393.7969+ | Windows Server 2012 R2: Apply CVE-2025-2663

  1. 1. Identify the current Windows version by running `winver` or checking System Properties
  2. 2. For Windows 10 1507 (build < 10240.20978): Upgrade to build 10240.20978 or later via Windows Update or Media Creation Tool
  3. 3. For Windows 10 1607 (build < 14393.7969): Upgrade to build 14393.7969 or later via Windows Update
  4. 4. For Windows 10 22h2 (build < 19045.5737): Upgrade to build 19045.5737 or later via Windows Update
  5. 5. For Windows 11 22h2 (build < 22621.5189): Upgrade to build 22621.5189 or later via Windows Update
  6. 6. For Windows 11 23h2 (build < 22631.5189): Upgrade to build 22631.5189 or later via Windows Update
  7. 7. For Windows 11 24h2 (build < 26100.3775): Upgrade to build 26100.3775 or later via Windows Update
  8. 8. For Windows Server 2016 (build < 14393.7969): Apply KB5055527 or later via Windows Update
Caveat Windows Server 2012 R2 reached end of support; consider migrating to a supported Windows Server version for continued security updates

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26637 — 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-26637 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