CVE-2025-26644Public exploit

Local authentication bypass via adversarial NIR video

Published Apr 8, 2025 · Updated Aug 10, 2026

A facial-recognition weakness in Windows Hello on affected Windows builds allows local users to bypass authentication with a crafted NIR video. The face matcher accepts identity-preserved near-infrared video presented on a custom LCD as a live authorized face instead of rejecting the adversarial input. Physical access, a compatible infrared camera, victim facial imagery, and specialized display hardware are required; success grants access as the enrolled user.

CVSS severity5.1
Medium
EPSS probability0.55%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

A facial-recognition weakness in Windows Hello on affected Windows builds allows local users to bypass authentication with a crafted NIR video. The face matcher accepts identity-preserved near-infrared video presented on a custom LCD as a live authorized face instead of rejecting the adversarial input. Physical access, a compatible infrared camera, victim facial imagery, and specialized display hardware are required; success grants access as the enrolled user.

The record

CVE
CVE-2025-26644
Published
Apr 8, 2025
Updated
Aug 10, 2026
Vendor
Microsoft
Product
Windows Server 2019
Classifications
CWE-1039
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 8, 2025CVE publishedPublication date reported by the CVE source.
  2. Aug 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0.17763.0 <10.0.17763.7136

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Microsoft · Windows Server 2019version=10.0.17763.0 <10.0.17763.7136
Microsoft · Windows Server 2025 (Server Core installation)version=10.0.26100.0 <10.0.26100.3775
Microsoft · Windows 11, version 24H2version=10.0.26100.0 <10.0.26100.3775
Microsoft · Windows 10 Version 21H2version=10.0.19044.0 <10.0.19044.5737
Microsoft · Windows 11 Version 22H3version=10.0.22631.0 <10.0.22631.5189
Microsoft · Windows 10 Version 22H2version=10.0.19045.0 <10.0.19045.5737
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.17763.0 <10.0.17763.7136
Microsoft · Windows 11 Version 23H2version=10.0.22631.0 <10.0.22631.5189
Microsoft · Windows 11, version 22H2version=10.0.22621.0 <10.0.22621.5189
Microsoft · Windows Server 2025version=10.0.26100.0 <10.0.26100.3775
Microsoft · Windows 10 Version 1809version=10.0.17763.0 <10.0.17763.7136

Published CVSS scores

5.1MicrosoftCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-1039Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo