dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-26162

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.14393.9060 / 10.0.17763.8644 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Access of resource using incompatible type ('type confusion') in Windows OLE 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 confidence

This is a type confusion vulnerability in Windows OLE (Object Linking and Embedding) that allows a locally authorized attacker to elevate privileges. Type confusion occurs when code treats an object of one type as a different, incompatible type, which can lead to memory corruption and privilege escalation.

MitigationApply the relevant Microsoft Windows security update when released through Windows Update or your organization's patch management process.

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
Windows 10 1607Operating system
Affected:< 10.0.14393.9060
Windows 10 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' from the Run dialog or execute 'systeminfo' in Command Prompt and note the OS Name, Version, and Build number
    Affected if The build number falls below any of these thresholds: 14393.9060, 17763.8644, 19044.7184, 19045.7184, 22631.6936, 26100.8246, 26200.8246, or 28000.1836 depending on your Windows 10/11 release
  2. Confirm Windows 10 or 11 edition
    Check if the system is running Windows 10 or Windows 11 by running 'winver' or checking system properties. This vulnerability affects only these desktop editions, not Server editions
    Affected if Running Windows 10 or Windows 11 desktop editions with builds below the thresholds listed in step 1
  3. Verify OLE component is present
    Check for the presence of OLE components by looking for ole32.dll or oleaut32.dll in C:\Windows\System32\ or by checking registry key HKLM\SOFTWARE\Microsoft\Ole
    Affected if OLE is a core Windows component and is typically present by default on desktop editions; absence would mean not affected
  4. Check for recent security updates
    Open Settings > Windows Update > Update history and look for security updates installed around the patch date for this CVE, or run 'wmic qfe list' to query installed hotfixes
    Affected if No security update addressing this CVE has been installed and the Windows version/build is below the affected thresholds

You are affected if your Windows 10 or 11 system has a build number lower than the threshold for your specific release and the corresponding security update has not been installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.14393.9060 / 10.0.17763.8644 / 10.0.19044.7184 or later
Fixed in 10.0.14393.906010.0.17763.864410.0.19044.7184
Interim mitigation

Apply the relevant Microsoft Windows security update when released through Windows Update or your organization's patch management process.

Recommended fix High confidence

Install the relevant Windows security update containing the fix (builds: 10.0.14393.9060+, 10.0.17763.8644+, 10.0.19044.7184+, 10.0.19045.7184+, 10.0.22631.6936+, 10.0.26100.8246+, 10.0.26200.8246+, 10.0.28000.1836+)

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest cumulative security update
  3. Alternatively, manually install the update from Microsoft Catalog by searching for the specific KB that addresses CVE-2026-26162
  4. Restart the system after the update is installed
  5. Verify the update was successful by checking the installed updates list or running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows edition
Caveat Standard Windows update risks apply - ensure backups and system restore points exist before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26162 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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