Skip to main content
Vulnerability Database/CVE-2026-85807

CVE-2026-85807: Windows USB Video Driver Privilege Escalation

CVE-2026-85807 is a privilege escalation vulnerability in Windows USB Video Driver caused by integer overflow. Authorized attackers can exploit this flaw to gain elevated privileges locally. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-85807 Overview

CVE-2026-85807 is an integer overflow vulnerability in the Windows USB Video Driver. An authorized local attacker can trigger the overflow to elevate privileges on an affected Windows host. The flaw is classified under [CWE-190] (Integer Overflow or Wraparound) and carries a CVSS 3.1 base score of 7.8.

Successful exploitation yields high impact to confidentiality, integrity, and availability. Attackers who gain SYSTEM-level execution through this driver can disable security controls, install persistence, and move laterally. Microsoft published the advisory on October 13, 2026.

Critical Impact

Local attackers with low privileges can elevate to SYSTEM by exploiting an integer overflow in the Windows USB Video Driver, gaining full control over the affected host.

Affected Products

  • Windows USB Video Driver (usbvideo.sys) — specific Windows versions enumerated in the Microsoft advisory
  • Windows client and server editions shipping the vulnerable USB Video Class (UVC) driver
  • Systems with USB video peripherals or virtual UVC devices accessible to local users

Discovery Timeline

  • 2026-10-13 - Microsoft published the CVE-2026-85807 advisory
  • 2026-10-13 - CVE-2026-85807 published to the National Vulnerability Database (NVD)
  • 2026-10-14 - Last updated in the NVD database

Technical Details for CVE-2026-85807

Vulnerability Analysis

The vulnerability resides in the Windows USB Video Driver, which handles USB Video Class (UVC) devices such as webcams and capture cards. An integer overflow occurs during the processing of attacker-controlled values, likely tied to buffer size or descriptor length calculations in the driver's I/O path.

When the arithmetic wraps, the driver allocates or indexes memory based on a truncated value. Subsequent writes operate on an undersized buffer, producing a kernel-mode memory corruption primitive. An authorized user who can reach the driver's interface can convert this primitive into arbitrary kernel execution.

Because the issue sits in a kernel driver loaded on most Windows installations, successful exploitation returns SYSTEM privileges. The attack does not require user interaction and runs with low complexity once a local foothold is obtained.

Root Cause

The root cause is an integer overflow or wraparound [CWE-190] in a size or length calculation inside the USB Video Driver. The driver fails to validate that an arithmetic operation on untrusted inputs stays within the bounds of the target integer type, leading to a smaller-than-expected allocation or index.

Attack Vector

The attack vector is local (AV:L) and requires low privileges (PR:L) with no user interaction. An attacker executes code as a standard user, then issues crafted IOCTLs or device requests to the vulnerable driver. The malformed input triggers the overflow and corrupts kernel memory to achieve privilege escalation.

Exploitation does not require a physical USB device. A local attacker can reach the driver through standard device interfaces or through virtual UVC endpoints exposed to user mode. Technical specifics are limited to the Microsoft advisory at the time of publication. See the Microsoft CVE-2026-85807 Advisory for vendor details.

Detection Methods for CVE-2026-85807

Indicators of Compromise

  • Unexpected processes spawning with SYSTEM or elevated tokens from parent processes running as standard users
  • Crashes or bugchecks referencing usbvideo.sys in Windows Error Reporting or minidumps
  • Unusual loading of unsigned or recently dropped binaries following USB device I/O activity

Detection Strategies

  • Monitor kernel-mode crashes and driver faults tied to usbvideo.sys, which can indicate failed exploitation attempts.
  • Correlate token elevation events (Event ID 4672, 4688) with the parent process context to surface anomalous privilege transitions.
  • Hunt for IOCTL enumeration patterns against USB video device objects originating from non-media applications.

Monitoring Recommendations

  • Enable kernel event tracing and forward Sysmon driver-load and process-creation events to a centralized data lake.
  • Baseline normal UVC driver interactions on endpoints so deviations stand out.
  • Alert on new scheduled tasks, services, or persistence artifacts created immediately after USB video driver anomalies.

How to Mitigate CVE-2026-85807

Immediate Actions Required

  • Apply the Microsoft security update for CVE-2026-85807 to all affected Windows systems during the next patch cycle.
  • Prioritize patching on multi-user systems, developer workstations, and jump hosts where local accounts are more common.
  • Restrict interactive and remote local logon rights to reduce the pool of users who can reach the vulnerable driver.

Patch Information

Microsoft addressed CVE-2026-85807 through the October 2026 security update cycle. Administrators should consult the Microsoft CVE-2026-85807 Advisory for the authoritative list of affected builds and corresponding KB articles, then deploy the updates through Windows Update, WSUS, Microsoft Intune, or Configuration Manager.

Workarounds

  • Disable or uninstall the USB Video Class driver on systems that do not require webcams or UVC capture devices.
  • Enforce device control policies that block attachment and use of USB video peripherals for non-essential endpoints.
  • Apply application control (for example, Windows Defender Application Control) to prevent unauthorized binaries from executing and staging local exploits.
bash
# Example: audit systems for the vulnerable driver version via PowerShell
Get-WmiObject Win32_PnPSignedDriver | Where-Object { $_.DeviceName -like "*USB Video*" } | Select DeviceName, DriverVersion, DriverDate

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.