dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-35417

HIGH · 7.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.17763.8755 / 10.0.19044.7291 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
Use after free 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 use-after-free vulnerability exists in the Windows Win32K graphics subsystem (GRFX) component that allows a locally authenticated attacker to elevate privileges to higher permission levels. The vulnerability involves improper memory management where memory is accessed after it has been freed, leading to potential arbitrary code execution in kernel context.

MitigationApply Microsoft security updates for CVE-2026-35417 when available. Prioritize patching systems with direct user access as the attacker requires local access to exploit this vulnerability.

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 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113
Windows Server 2019Operating system
Affected:< 10.0.17763.8755

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. Check Windows version and build number
    Open Command Prompt or PowerShell and run: winver or systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"Build Number". Alternatively, run 'ver' command to get the exact version string.
    Affected if The installed version falls below any of these thresholds: Windows 10 1809/Server 2019 < 10.0.17763.8755; Windows 10 21h2 < 10.0.19044.7291; Windows 10 22h2 < 10.0.19045.7291; Windows 11 23h2 < 10.0.22631.7079; Windows 11 24h2 < 10.0.26100.8390; Windows 11 25h2 < 10.0.26200.8390; Windows 11 26h1 < 1
  2. Verify Win32K.sys version
    Locate the win32k.sys file in C:\Windows\System32\drivers\ and check its file version property, or run 'powershell (Get-Item C:\Windows\System32\drivers\win32k.sys).VersionInfo' to retrieve version details.
    Affected if The win32k.sys version is older than the version corresponding to the patched build for your Windows release.
  3. Confirm security update installation
    Open Settings > Windows Update > View update history, or run 'powershell Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recently installed updates. Look for the security update containing CVE-2026-35417.
    Affected if The CVE-2026-35417 security update is not listed among installed updates.

Your environment is affected if the installed Windows version or Win32K.sys version is below the specified build thresholds AND the CVE-2026-35417 security update has not been applied.

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.17763.8755 / 10.0.19044.7291 / 10.0.19045.7291 or later
Fixed in 10.0.17763.875510.0.19044.729110.0.19045.7291
Interim mitigation

Apply Microsoft security updates for CVE-2026-35417 when available. Prioritize patching systems with direct user access as the attacker requires local access to exploit this vulnerability.

Recommended fix High confidence

Windows 10 1809: build 10.0.17763.8755 | Windows 10 21h2: build 10.0.19044.7291 | Windows 10 22h2: build 10.0.19045.7291 | Windows 11 23h2: build 10.0.22631.7079 | Windows 11 24h2: build 10.0.26100.8390 | Windows 11 25h2: build 10.0.26200.8390 | Windows 11 26h1: build 10.0.28000.2113 | Windows Serve

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows version and build you are running (e.g., Windows 10 22h2, Windows 11 23h2, etc.)
  3. Navigate to Windows Update by opening Settings > Update & Security > Windows Update
  4. Check for updates and install all available security updates
  5. Alternatively, manually download and install the specific cumulative update for your Windows version from the Microsoft Update Catalog matching the fixed build number for your release
  6. Restart the system after applying updates
  7. Verify the update was successful by checking the installed updates via 'appwiz.cpl' or by running 'winver' to confirm the build number matches or exceeds the fixed version
Caveat Standard Windows cumulative update apply with no expected breaking changes; as a kernel security update, ensure compatibility with existing drivers and software

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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