dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-26178

HIGH · 8.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 →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Integer size truncation in Windows Advanced Rasterization Platform (WARP) allows an unauthorized 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 local privilege escalation vulnerability in Windows Advanced Rasterization Platform (WARP), a software rasterizer used for graphics rendering. The vulnerability involves integer size truncation, where a larger integer value is improperly reduced in size, potentially causing memory corruption or unexpected behavior that can be exploited to gain elevated (SYSTEM) privileges on the affected system.

MitigationApply the Microsoft security update for CVE-2026-26178 as soon as practical; until patched, limit local access to trusted users only and monitor for suspicious processes.

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 Server 2016Operating system
Affected:< 10.0.14393.9060

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Check Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'. Compare the build number (e.g., 14393, 17763, 19044, 19045, 22631, 26100, 26200) and full version (e.g., 10.0.14393.9060) against the affected version ranges listed for your Windows edition.
    Affected if The installed build number and full version fall below the patched versions: Windows 10 1607/Server 2016 < 10.0.14393.9060, Windows 10 1809 < 10.0.17763.8644, Windows 10 21h2 < 10.0.19044.7184, Windows 10 22h2 < 10.0.19045.7184, Windows 11 23h2 < 10.0.22631.6936, Windows 11 24h2 < 10.0.26100.8246, W
  2. Verify WARP rasterizer component is present
    Check for the presence of WARP-related graphics files. In PowerShell, run 'Get-ItemProperty -Path "C:\Windows\System32\d3d10warp.dll" -ErrorAction SilentlyContinue' to verify the WARP software rasterizer DLL exists on the system.
    Affected if The d3d10warp.dll file exists (this is the WARP rasterizer, which is a default Windows component; its presence indicates the vulnerable attack surface exists on the system).
  3. Check WARP driver file version
    Right-click d3d10warp.dll in C:\Windows\System32\, select Properties, then go to the Details tab to view the File Version. Alternatively, in PowerShell run '(Get-Item "C:\Windows\System32\d3d10warp.dll").VersionInfo.FileVersion'.
    Affected if The file version of d3d10warp.dll is lower than the versions corresponding to the security update for this CVE (the specific version numbers vary by Windows build but correspond to the patched builds listed in the affected versions).
  4. Confirm Windows Update patch status
    Open Settings > Windows Update > View update history, or run 'wmic qfe list' in Command Prompt to list installed hotfixes. Look for security updates installed around the CVE-2026-26178 patch date.
    Affected if The system is missing the specific Microsoft security update for CVE-2026-26178, and the Windows version falls within the affected version ranges.

You are affected if your Windows version and build number are within the affected ranges AND the WARP component (d3d10warp.dll) is present AND the corresponding security update for CVE-2026-26178 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 Microsoft security update for CVE-2026-26178 as soon as practical; until patched, limit local access to trusted users only and monitor for suspicious processes.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.9060 | Windows 10 1809: 10.0.17763.8644 | Windows 10 21h2: 10.0.19044.7184 | Windows 10 22h2: 10.0.19045.7184 | Windows 11 23h2: 10.0.22631.6936 | Windows 11 24h2: 10.0.26100.8246 | Windows 11 25h2: 10.0.26200.8246 | Windows Server 2016: 10.0.14393.9060

  1. 1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Based on the identified version, determine the minimum required build number from the fixed versions list
  3. 3. Open Windows Settings > Update & Security > Windows Update
  4. 4. Click 'Check for updates' to download and install the latest security updates
  5. 5. After installation, restart the computer when prompted
  6. 6. Verify the update was successful by checking the Windows version again - the build number should now be equal to or higher than the fixed version for your Windows edition
Caveat Standard Windows update - minimal risk; ensure backups of critical data before any system update as standard practice

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26178 — 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-26178 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