CVE-2026-50410
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 Runtime 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 confidenceA Use After Free (UAF) vulnerability in the Windows Runtime component allows a locally authorized attacker to manipulate freed memory, potentially achieving elevated privileges. This memory corruption issue stems from improper memory management during Windows Runtime object lifecycle handling.
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.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525< 10.0.17763.9020< 10.0.20348.5386CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows 10 version build numberRun 'winver' or 'systeminfo' and note the Build number displayed (e.g., 10.0.17763.xxx)Affected if Build number is less than 10.0.17763.9020 on Windows 10 1809, less than 10.0.19044.7548 on 21h2, or less than 10.0.19045.7548 on 22h2
-
Check Windows 11 version build numberRun 'winver' or 'systeminfo' and note the Build number displayedAffected if Build number is less than 10.0.26100.8875 on 24h2, less than 10.0.26200.8875 on 25h2, or less than 10.0.28000.2525 on 26h1
-
Check Windows Server versionRun 'systeminfo' and check the OS Name and Version fields for Server 2019 or Server 2022Affected if Running Windows Server 2019 with build below 10.0.17763.9020, or Windows Server 2022 with build below 10.0.20348.5386
If the installed Windows build number falls below any of the specified thresholds for your Windows version (10, 11, or Server), the environment is vulnerable to this UAF in Windows Runtime.
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.
dbcve · scoped10.0.17763.902010.0.19044.754810.0.19045.7548
Apply Microsoft security updates for Windows Runtime once released. Verify that all local user accounts have appropriate least-privilege access to reduce attack surface.
Upgrade to Windows 10 1809 build 10.0.17763.9020 or later; Windows 10 21h2 build 10.0.19044.7548 or later; Windows 10 22h2 build 10.0.19045.7548 or later; Windows 11 24h2 build 10.0.26100.8875 or later; Windows 11 25h2 build 10.0.26200.8875 or later; Windows 11 26h1 build 10.0.28000.2525 or later; W
- Open Settings > Update & Security > Windows Update and check for updates
- Alternatively, run 'ms-settings:windowsupdate' from the Run dialog
- For enterprise deployments, use Windows Server Update Services (WSUS), Microsoft Intune, or Group Policy to deploy the latest Windows security updates
- Verify the installed build version matches or exceeds the fixed version for your Windows release (e.g., winver command to check)
- Ensure the system reboots after applying the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50410 — 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-50410 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