dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-33104

HIGH · 7.0 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 →
72/100
Remediation priority · Elevated
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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Win32K - GRFX 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

A race condition vulnerability in the Windows Win32K graphics subsystem (GRFX) allows an authorized local attacker to exploit improper synchronization when accessing shared resources, enabling privilege escalation from a standard user to higher privileges on the affected system.

MitigationApply the relevant Microsoft security update for this vulnerability through Windows Update or the Microsoft Security Update Catalog. Prioritize patching systems with local user access where privilege escalation could occur.

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

CVSS:3.1/AV:L/AC:H/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. Check Windows build version
    Run 'winver' or 'systeminfo | findstr /C:"Build"' to obtain the current Windows build number
    Affected if Build number is below 14393.9060 for Windows 10 1607, below 17763.8644 for 1809, below 19044.7184 for 21h2, below 19045.7184 for 22h2, below 22631.6936 for Windows 11 23h2, below 26100.8246 for 24h2, below 26200.8246 for 25h2, or below 28000.1836 for 26h1
  2. Verify win32k.sys version
    Check the file version of win32k.sys located in C:\Windows\System32\drivers\win32k.sys by viewing its Properties > Details
    Affected if The file version is lower than the version corresponding to the fixed build numbers for your Windows release
  3. Confirm graphics subsystem is active
    Run 'driverquery /v | findstr -i win32k' to verify the Win32K graphics driver is loaded
    Affected if The win32k.sys driver is present and running, which is the default state on Windows desktop editions

The system is vulnerable if it runs an unpatched Windows version with a build number below the fixed thresholds and has the Win32K graphics subsystem enabled, which is the default configuration.

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 security update for this vulnerability through Windows Update or the Microsoft Security Update Catalog. Prioritize patching systems with local user access where privilege escalation could occur.

Recommended fix Moderate 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 11 26h1: 10.0.28000.1836

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Update: Settings > Update & Security > Windows Update
  3. Click 'Check for updates' and install all available updates
  4. Alternatively, download the specific security update from Microsoft Update Catalog matching your Windows version (KB references can be found on msrc.microsoft.com)
  5. Restart the system after updates are installed
  6. Verify the installed version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update - minimal risk; ensure backups of critical data before applying updates as with any system modification

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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