CVE-2026-50687
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 · uneditedUse after free in Windows Kernel allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 confidenceThis is a use-after-free vulnerability in the Windows Kernel that allows a local attacker to elevate privileges. The vulnerability occurs when the kernel continues to use a memory pointer after it has been freed, potentially enabling arbitrary code execution at elevated privilege levels.
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.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525< 10.0.26100.33158CVSS 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.
-
Identify Windows version and build numberRun 'winver' from command prompt or check 'System Information' (msinfo32). Note the version and build number displayed.Affected if The build number is lower than 10.0.26100.8875 for 24h2, lower than 10.0.26200.8875 for 25h2, lower than 10.0.28000.2269 or 10.0.28000.2525 for 26h1, or lower than 10.0.26100.33158 for Server 2025.
-
Verify exact system build with systeminfoRun 'systeminfo' from command prompt and locate the 'OS Version' line. This shows the full version string including the build number in format like '10.0.26100.xxxx'.Affected if The build number shown is within the affected ranges listed above.
-
Confirm Windows edition is affectedCheck if the system is Windows 11 (any edition) or Windows Server 2025. Run 'winver' to see the Windows edition or check 'System Information' for 'OS Name'.Affected if The system is Windows 11 24h2, 25h2, 26h1, or Windows Server 2025 and the build number is below the fixed versions.
-
Check architectureRun 'echo %PROCESSOR_ARCHITECTURE%' or check 'System Information' for 'System Type'. This is a kernel vulnerability that typically affects 64-bit systems.Affected if Running 64-bit Windows (amd64) within the affected version ranges.
A system is affected if it runs Windows 11 24h2, 25h2, 26h1, or Windows Server 2025 with a build number lower than the fixed versions specified for each release.
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.
From vendor data10.0.26100.887510.0.26100.3315810.0.26200.8875
Apply Microsoft security updates immediately upon release. Ensure all affected Windows systems are patched and consider implementing least-privilege policies to limit local attack surface.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50687 — 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-50687 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