CVE-2026-49804
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHeap-based buffer overflow in Windows USB Video Driver allows an unauthorized attacker to elevate privileges with a physical attack.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceHeap-based buffer overflow in the Windows USB Video Driver allows an attacker to corrupt heap memory via specially crafted USB video device requests, leading to privilege escalation from user mode to elevated (SYSTEM) privileges. The physical attack requirement indicates the attacker needs local access to connect a malicious USB device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.14393.9339< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875all versions= r2< 10.0.14393.9339CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Windows version and build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows version and build numberAffected if The build number falls below the patched versions: 14393.9339 (Win10 1607), 17763.9020 (Win10 1809), 19044.7548 (Win10 21h2), 19045.7548 (Win10 22h2), 26100.8875 (Win11 24h2), or 26200.8875 (Win11 25h2)
-
Confirm Windows Server edition and buildRun 'systeminfo' and check the OS Name and OS Version fields for Windows Server 2012 (any build) or Windows Server 2016 with build below 14393.9339Affected if Running Windows Server 2012 any version, Windows Server 2012 R2 any version, or Windows Server 2016 with build lower than 14393.9339
-
Verify USB Video Driver is presentCheck if the USB Video Driver (usbvideo.sys) exists by running 'driverquery /v | findstr usbvideo' or checking C:\Windows\System32\drivers\usbvideo.sysAffected if The usbvideo.sys driver is loaded on the system (vulnerability only applies if this driver is present)
-
Assess physical access exposureReview system security posture: check if workstations or servers have uncontrolled physical USB access, run 'net session' to confirm if running in an elevated administrative context, and evaluate whether untrusted USB devices could be connectedAffected if The system has physical USB exposure and the user has ability to connect devices, combined with a vulnerable OS version
The system is affected if running a Windows version or Server edition with a build number lower than the patched versions listed, and the USB Video Driver is present with physical USB access possible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.14393.933910.0.17763.902010.0.19044.7548
Apply Microsoft security updates for the Windows USB Video Driver once released; restrict physical access to critical systems; disable unused USB ports if possible.
Upgrade to the specified cumulative update version for your Windows release (e.g., Windows 10 1809 to build 10.0.17763.9020, Windows 11 24h2 to build 10.0.26100.8875); migrate Windows Server 2012/R2 to a supported Windows Server version
- Open Settings > Update & Security > Windows Update and check for available updates
- Install the cumulative security update for your specific Windows version
- For Windows 10 1607: Update to version 10.0.14393.9339 or later
- For Windows 10 1809: Update to version 10.0.17763.9020 or later
- For Windows 10 21h2: Update to version 10.0.19044.7548 or later
- For Windows 10 22h2: Update to version 10.0.19045.7548 or later
- For Windows 11 24h2: Update to version 10.0.26100.8875 or later
- For Windows 11 25h2: Update to version 10.0.26200.8875 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49804 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49804 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data