CVE-2025-26644
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 · uneditedAutomated recognition mechanism with inadequate detection or handling of adversarial input perturbations in Windows Hello allows an unauthorized attacker to perform spoofing locally.
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 confidenceWindows Hello's biometric authentication (facial recognition or fingerprint) has inadequate detection of adversarial input perturbations, allowing a local attacker to spoof the biometric authentication using crafted inputs such as photos or replica fingerprints.
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.7136< 10.0.19044.5737< 10.0.19045.5737< 10.0.22621.5189< 10.0.22631.5189< 10.0.26100.3775< 10.0.17763.7136< 10.0.26100.3775CVSS 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
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Verify if Windows Hello biometric authentication is enabledOpen Settings > Accounts > Sign-in options and check if Windows Hello Face or Windows Hello Fingerprint is listed under 'Ways to sign in' with status 'On' or if biometric credentials are enrolled.Affected if Biometric authentication (face or fingerprint) is enrolled and enabled - the vulnerability only applies when Windows Hello uses biometric verification.
-
Check installed Windows versionRun 'winver' from the Run dialog or execute 'systeminfo' in Command Prompt and note the OS Version and Build number shown (e.g., 10.0.19045.5737).Affected if The installed version and build number fall below the fixed versions for the respective Windows release (1809: <10.0.17763.7136, 21h2: <10.0.19044.5737, 22h2: <10.0.19045.5737, 11 22h2: <10.0.22621.5189, 11 23h2: <10.0.22631.5189, 11 24h2: <10.0.26100.3775, Server 2019: <10.0.17763.7136, Server 2025
-
Confirm Windows release branchRun 'winver' and note the specific release (such as 'Version 22H2', 'Version 23H2', 'Version 24H2', or 'Windows Server 2025') displayed in the about window, as version numbers alone may overlap across different releases.Affected if The detected release branch combined with its build number is below the corresponding patched threshold for that specific Windows release.
A system is affected if Windows Hello biometric authentication (face or fingerprint) is enabled and the installed Windows version/build is below the fixed version for that specific Windows release branch.
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.713610.0.19044.573710.0.19045.5737
Apply Microsoft security updates for Windows Hello; consider requiring PIN as an additional authentication factor until patches are deployed.
Windows 10 1809 (build 10.0.17763.7136+), Windows 10 21h2 (build 10.0.19044.5737+), Windows 10 22h2 (build 10.0.19045.5737+), Windows 11 22h2 (build 10.0.22621.5189+), Windows 11 23h2 (build 10.0.22631.5189+), Windows 11 24h2 (build 10.0.26100.3775+), Windows Server 2019 (build 10.0.17763.7136+), Wi
- Check current Windows version by running `winver` or `systeminfo`
- Identify which Windows 10 or 11 version or Windows Server 2019/2025 build is currently installed
- Apply Windows updates to obtain the security update containing the fix, or download and install the appropriate Cumulative Update for your Windows version from Microsoft Update Catalog
- For Windows 10 1809: Update to build 10.0.17763.7136 or later
- For Windows 10 21h2: Update to build 10.0.19044.5737 or later
- For Windows 10 22h2: Update to build 10.0.19045.5737 or later
- For Windows 11 22h2: Update to build 10.0.22621.5189 or later
- For Windows 11 23h2: Update to build 10.0.22631.5189 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26644 — 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-26644 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