Skip to main content

Windows USB Video Driver EUVDEUVD-2026-99478

| CVE-2026-85341 HIGH
Heap-based Buffer Overflow (CWE-122)
2026-10-13 secure@microsoft.com GHSA-mq69-w372-3vgv
7.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged local access
  2. Delivery
    Invoke crafted request to USB Video Driver
  3. Exploit
    Trigger heap-based buffer overflow in kernel
  4. Execution
    Corrupt kernel memory and hijack execution
  5. Impact
    Elevate to SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to already hold a low-privileged authenticated local account on the target host (PR:L) with the ability to run code that reaches the Windows USB Video Driver's affected code path; no user interaction (UI:N) and no network access are involved. The principal limiting factor is the local-only attack vector - there is no remote trigger - which confines risk to multi-user systems, shared/terminal hosts, or post-initial-access scenarios; a user who cannot execute code locally cannot exploit this. All listed Windows 10, 11 (21H2 through 26H2), and Windows Server 2012 through 2025 builds below the fixed versions are affected, so patching to the fixed build (e.g., Windows 11 24H2 ≥10.0.26100.9711) removes the condition.

Impact

This is a credible but moderate-priority local privilege-escalation issue rather than an urgent emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) describes a local, low-complexity attack by an already-authenticated low-privileged user that yields full confidentiality, integrity and availability impact (SYSTEM-level compromise) on the affected host. CISA's SSVC framework corroborates this profile: Exploitation is 'none' (no observed or public exploitation), Automatable is 'no' (consistent with AV:L requiring pre-existing local access, so it cannot be sprayed at scale), yet Technical Impact is 'total' (matching the C:H/I:H/A:H full-system compromise). All signals are mutually consistent - there is no network vector despite the high impact, and no evidence of in-the-wild use. Note what is MISSING: no EPSS score was provided, so exploitation probability cannot be quantified; the CVE is not in CISA KEV; and no POC was supplied. The combination (local-only vector, non-automatable, no exploitation evidence) means this is a real but second-tier patch priority - important for multi-user hosts, terminal servers, and environments where untrusted users have interactive access, but not an internet-facing drive-by risk.

Exploit ScenarioDerived

An attacker who already has a low-privileged local account (or has achieved initial code execution as a standard user) runs a crafted program that interacts with the Windows USB Video Driver, sending malformed data that overflows a heap buffer to corrupt kernel memory and execute code as SYSTEM. Because the CVSS vector is AV:L/PR:L/UI:N, no network access or user interaction is needed, but the attacker must first have local authenticated access. No public exploit code was identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Local privilege escalation in the Windows USB Video Driver allows an authenticated attacker holding a low-privileged account on the target host to trigger a heap-based buffer overflow (CWE-122) and gain high-integrity/kernel-level code execution. Affected software spans Windows 10 (1607 through 22H2), Windows 11 (21H2 through 26H2), and Windows Server 2012 through 2025 builds below their respective fixed versions, per the vendor's affected-version data. Exploitation is local-only (AV:L/PR:L/UI:N), so it requires pre-existing code execution on the host and is not remotely reachable; no public exploit code has been identified at time of analysis, CISA's SSVC assessment records Exploitation: none, and there is no KEV listing, making this a credible but moderate-priority privilege-escalation issue rather than an emergency. Microsoft has released patches ("Available from vendor") and all affected builds have published fixed version numbers.

RemediationAI

Apply the Microsoft vendor patch listed in the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85341); patching is the primary and sufficient fix and the vendor has published exact fixed builds for every affected branch, for example Windows 11 24H2 to 10.0.26100.9711, Windows 11 23H2 to 10.0.22631.7652, Windows 10 21H2/22H2 to 10.0.19044.7807, Windows Server 2025 to 10.0.26100.33650, Windows Server 2022 to 10.0.20348.5761, Windows Server 2019 and Windows 10 1809 to 10.0.17763.9376, Windows Server 2016 and Windows 10 1607 to 10.0.14393.9612, and legacy Windows Server 2012/2012 R2 to 6.2.9200.26434 and 6.3.9600.23470. Prioritize hosts where multiple low-privileged users can execute code, since the vector is local-only; because no public exploit code or active exploitation has been identified (SSVC Exploitation: none, no KEV listing), emergency out-of-band action is not warranted, and the fix can be delivered through normal monthly update cycles. Where patching must be deferred, apply compensating controls that specifically shrink local attack surface: remove or disable the USB video capture device class (usbvideo.sys) on server and kiosk images that have no cameras, accepting that webcams, capture cards, and virtual-camera software will stop working; enforce Device Installation Restrictions via Group Policy to block installation of untrusted or unknown USB Video Class devices, at the cost of administrative overhead and potential blocking of legitimate peripherals; and reduce the number of accounts able to run arbitrary code on shared/terminal hosts and monitor for kernel pool-corruption or privilege-escalation behavior from non-administrative processes. Note that blocking physical USB ports is only partial mitigation, since a local process can still reach the driver's code path without a newly attached device.

Affected VersionsENISA

Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows Server 2019 10.0.17763.0 <10.0.17763.9376

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2012 fix: 6.2.9200.26434
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26434
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 20 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a heap-based buffer overflow (CWE-122) in the Windows USB Video Driver, the kernel-mode component (usbvideo.sys class driver stack) that services USB Video Class (UVC) devices such as webcams, capture cards, and virtual cameras. In this defect class, the driver allocates a pool block based on one size calculation and then writes past its boundary when parsing or copying attacker-influenced data - typically device descriptors, stream/format negotiation structures, or isochronous video payloads - resulting in corruption of adjacent kernel pool memory. Because the affected code runs in kernel mode, successful corruption can be shaped into controlled pool metadata manipulation and eventual arbitrary kernel execution, which is why the CVSS vector rates Confidentiality/Integrity/Availability all High with Scope Unchanged. The attack vector is local (AV:L) with low privileges required (PR:L) and no user interaction (UI:N); AC:L indicates no unusual preconditions beyond reaching the vulnerable code path. Reachability can come either from a locally running process issuing IOCTLs/device I/O to the video driver or from a physically or virtually attached USB video device presenting malformed descriptors - the local vector simply means the attacker must already be executing on the machine (or control an attached device), not that a network path exists.

Know when Windows gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local-only kernel driver flaw exploitable by any authenticated low-privileged user with no user interaction, yielding full SYSTEM compromise, so AV:L/PR:L and C/I/A all High.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:20 cve.org
HIGH 7.8

DescriptionCVE.org

Heap-based buffer overflow in Windows USB Video Driver allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A local privilege-escalation vulnerability in the Windows USB Video Driver affects supported Windows 10, Windows 11, and Windows Server builds, allowing an authenticated low-privileged local user to gain kernel-level code execution. No public exploit identified at time of analysis, and because exploitation requires prior access to a host, the immediate organizational risk is contained, but unpatched systems still present a path for an attacker with a foothold to expand control. Leadership should prioritize patching to prevent escalation from low-privileged access to full system compromise, particularly across broad Windows endpoint and server estates.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Ubiquitous
Core Windows component spanning Windows 10/11 and Server 2012-2025
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy