CVE-2026-50435
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 · uneditedBuffer over-read in Windows Overlay Filter 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 buffer over-read vulnerability exists in the Windows Overlay Filter component that allows a local, authorized attacker to read unintended memory contents and leverage this to elevate privileges to higher integrity 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.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.2525= 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.
-
Check Windows version and build numberRun 'winver' from the Run dialog or execute 'systeminfo' in Command Prompt and locate the OS Name and Version lines, or run 'winmgmt /savecreds' to get the exact build number via 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild'Affected if The build number is below 14393.9339 (Windows 10 1607), 17763.9020 (Windows 10 1809), 19044.7548 (Windows 10 21h2), 19045.7548 (Windows 10 22h2), 26100.8875 (Windows 11 24h2), 26200.8875 (Windows 11 25h2), 28000.2269 or 28000.2525 (Windows 11 26h1), or if running Windows Server 2012 R2
-
Confirm the specific Windows editionRun 'winver' or check System Properties to confirm whether the system is Windows 10 1607, 1809, 21h2, 22h2, Windows 11 24h2/25h2/26h1, or Windows Server 2012 R2Affected if The edition matches any of the affected versions listed in the CVE and the build number is below the corresponding patched threshold
-
Verify Windows Overlay Filter component presenceCheck for the presence of the Overlay Filter driver by examining '%SystemRoot%\System32\drivers\mf.sys' or searching for overlay filter related files in the Windows Media Player or multimedia components, or check via 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup"' for multimedia featuresAffected if The Overlay Filter component is installed on the system (this is a default component in affected Windows versions)
A system is affected if it runs any of the specified Windows 10 or Windows 11 versions (or Windows Server 2012 R2) with a build number below the patched thresholds AND has the Windows Overlay Filter component present.
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 affected Windows versions once released. Restrict local access to trusted users and monitor for privilege escalation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50435 — 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-50435 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