CVE-2026-50476
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 Microsoft Windows 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 Microsoft Windows enables a locally authorized attacker to elevate privileges. The vulnerability involves memory that is freed but still accessed, allowing an attacker with basic system access to gain higher privileges.
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.14393.9339< 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.2525all versions= r2CVSS 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 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the installed Windows version and build numberAffected if The displayed build number falls below the affected version thresholds for your Windows release (e.g., less than 10.0.14393.9339 for Windows 10 1607, less than 10.0.17763.9020 for Windows 10 1809, etc.)
-
Confirm Windows 10 releaseRun 'winver' to see the specific Windows 10 release name (such as 1607, 1809, 21h2, or 22h2) displayed in the About Windows dialogAffected if The release is 1607, 1809, 21h2, or 22h2 and the build number is below the corresponding threshold
-
Confirm Windows 11 releaseRun 'winver' to identify the Windows 11 feature update version (24h2, 25h2, or 26h1) shown in the About Windows dialogAffected if The release is 24h2, 25h2, or 26h1 and the build number is below 10.0.26100.8875, 10.0.26200.8875, or 10.0.28000.2269/10.0.28000.2525 respectively
-
Check Windows Server 2012 versionRun 'systeminfo' or 'winver' on Windows Server 2012 or Windows Server 2012 R2 systemsAffected if The system is running Windows Server 2012 or Windows Server 2012 R2 (all versions are affected per the advisory)
You are affected if your Windows system matches one of the listed versions AND your current build number is below the specified threshold for that release, or if you are running any version of Windows Server 2012/R2.
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.14393.933910.0.17763.902010.0.19044.7548
Apply Microsoft security updates for Windows when available; ensure least-privilege principles for local user accounts; monitor for suspicious processes attempting privilege escalation.
- Consultation4.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50476 — 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-50476 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