CVE-2026-41092
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 · uneditedImproper access control in Microsoft Kinect allows an authorized attacker to elevate privileges locally.
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 confidenceImproper access control in Microsoft Kinect (Windows SDK or driver components) allows a locally authenticated attacker to escalate privileges by exploiting insufficient permission validation in the sensor/kinect service, potentially gaining administrator or system-level access.
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.9234< 10.0.17763.8880< 10.0.19044.7417< 10.0.19045.7417< 10.0.22631.7219< 10.0.26100.8655< 10.0.26200.8655< 10.0.28000.2269CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Determine if Kinect software is installedOpen Programs and Features (appwiz.cpl) and search for 'Kinect' entries, or check for Kinect-related directories in Program Files. Alternatively, run 'Get-Package -ProviderName Programs -IncludeWindowsInstaller | Where-Object {$_.Name -like "*Kinect*"}' in PowerShell.Affected if Kinect for Windows SDK, Kinect Runtime, or any Kinect driver components are present on the system
-
Identify the installed Windows versionRun 'winver' from the Run dialog, or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt, or use 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion' in PowerShell.Affected if The Windows version falls within any of the affected ranges: Windows 10 1607 (<10.0.14393.9234), 1809 (<10.0.17763.8880), 21h2 (<10.0.19044.7417), 22h2 (<10.0.19045.7417); or Windows 11 23h2 (<10.0.22631.7219), 24h2 (<10.0.26100.8655), 25h2 (<10.0.26200.8655), 26h1 (<10.0.28000.2269)
-
Check for Kinect-related servicesOpen Services (services.msc) and look for any service with 'Kinect' in the name, or run 'Get-Service | Where-Object {$_.Name -like "*Kinect*"}' in PowerShell.Affected if A Kinect service (such as KinectManagement, KinectService, or similar) exists and is installed on the system
-
Verify the driver component presenceOpen Device Manager (devmgmt.msc), expand 'Kinect' or 'Sensors' categories if present, or run 'Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.Description -like "*Kinect*"}' in PowerShell.Affected if A Kinect sensor driver or device is listed in Device Manager
The system is affected if Kinect software, drivers, or services are installed AND the Windows version matches any of the listed affected ranges, as the privilege escalation requires the vulnerable Kinect component to be present.
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.923410.0.17763.888010.0.19044.7417
Apply available Microsoft security updates for Kinect; if no patch exists due to product discontinuation, consider disabling Kinect services or removing the software entirely to eliminate the attack vector.
Windows 10 1607: 10.0.14393.9234 | Windows 10 1809: 10.0.17763.8880 | Windows 10 21h2: 10.0.19044.7417 | Windows 10 22h2: 10.0.19045.7417 | Windows 11 23h2: 10.0.22631.7219 | Windows 11 24h2: 10.0.26100.8655 | Windows 11 25h2: 10.0.26200.8655 | Windows 11 26h1: 10.0.28000.2269 or later
- Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Determine which Windows 10 or 11 version and build you are currently running
- If running an affected version, apply Windows updates via Settings > Update & Security > Windows Update
- Alternatively, manually download and install the relevant cumulative update from the Microsoft Update Catalog for your specific Windows version
- Verify the update was successful by checking the Windows version matches or exceeds the fixed build number for your release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41092 — 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-41092 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