CVE-2026-69799

Local privilege escalation via shared-resource race

Published Sep 8, 2026 · Updated Sep 9, 2026

Race condition in Windows Hello on affected Windows 10 and 11 builds allows local users to elevate privileges. Microsoft identifies improper synchronization of a shared resource in Windows Hello but has not disclosed the resource, code locus, or conflicting operation. Exploitation requires existing low-privileged local access, no user interaction, and a high-complexity race; success crosses a security boundary and grants elevated privileges.

CVSS severity7.8
High
EPSS probability0.19%
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

Race condition in Windows Hello on affected Windows 10 and 11 builds allows local users to elevate privileges. Microsoft identifies improper synchronization of a shared resource in Windows Hello but has not disclosed the resource, code locus, or conflicting operation. Exploitation requires existing low-privileged local access, no user interaction, and a high-complexity race; success crosses a security boundary and grants elevated privileges.

The record

CVE
CVE-2026-69799
Published
Sep 8, 2026
Updated
Sep 9, 2026
Vendor
Microsoft
Product
Windows 11, version 25H2
Classifications
CWE-362, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 8, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 9, 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.26200.0 <10.0.26200.9445

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Microsoft · Windows 11, version 25H2version=10.0.26200.0 <10.0.26200.9445
Microsoft · Windows 11, version 24H2version=10.0.26100.0 <10.0.26100.9445
Microsoft · Windows 10 Version 21H2version=10.0.19044.0 <10.0.19044.7725
Microsoft · Windows 10 Version 22H2version=10.0.19045.0 <10.0.19045.7725
Microsoft · Windows 11, version 26H1version=10.0.28000.0 <10.0.28000.2954
Microsoft · Windows 11 Version 23H2version=10.0.22631.0 <10.0.22631.7582

Published CVSS scores

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

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)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

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