CVE-2026-83853: Windows Hello use after free privilege escalation

CVE-2026-83853 · Severity: high · CVSS 7 · Published 2026-10-13

Windows Hello is Microsoft's biometric authentication system used to secure user accounts on Windows devices. A use-after-free vulnerability allows an authorized local attacker to escalate their privileges on the system, potentially gaining administrative access and full control of the device.

Technologies: Microsoft Windows Hello. Vendors: Microsoft.

Quick answers

Is CVE-2026-83853 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-83853 being exploited in the wild.
How severe is CVE-2026-83853?
High severity, with a CVSS score of 7, published 13 October 2026.
Which products and versions are affected?
Microsoft Windows Hello.
Is there a fix for CVE-2026-83853?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-83853 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-83853?
Check whether you run Microsoft Windows Hello. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A use-after-free vulnerability exists in Windows Hello's memory management. An authenticated local attacker can exploit this flaw by manipulating memory to gain kernel-level privileges, bypassing normal privilege boundaries and achieving local privilege escalation.

Affected products

  • Microsoft Windows Hello

Timeline

  • 2026-10-13: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.