CVE-2026-50437
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 · uneditedOut-of-bounds read in Windows DWM Core Library allows an authorized attacker to disclose information 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 confidenceAn out-of-bounds read vulnerability exists in the Windows DWM Core Library (dwmcore.dll) that allows a local authorized attacker to read sensitive information from memory due to improper bounds checking when processing graphical objects or window metadata.
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< 10.0.14393.9339CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 build numberRun 'winver' or execute 'systeminfo | findstr /C:"Build"' in Command Prompt to obtain the Windows build versionAffected if The build number falls below the thresholds for your Windows release: 14393.9339 (Win10 1607/Server 2016), 17763.9020 (Win10 1809), 19044.7548 (Win10 21h2), 19045.7548 (Win10 22h2), 26100.8875 (Win11 24h2), 26200.8875 (Win11 25h2), or 28000.2269/28000.2525 (Win11 26h1)
-
Locate dwmcore.dll versionOpen File Explorer, navigate to C:\Windows\System32\dwmcore.dll, right-click and select Properties, then view the Details tab for the File versionAffected if The file version is not present or cannot be determined (dwmcore.dll missing from System32)
-
Compare dwmcore.dll version against affected buildsNote the Product version or File version from the dwmcore.dll Properties and compare it to the fixed build numbers listed for your Windows releaseAffected if The dwmcore.dll version is older than the fixed builds for your Windows version (meaning the DLL has not been patched)
-
Verify DWM service is runningOpen Services (services.msc), locate Desktop Window Manager Session Manager, and check if Status shows RunningAffected if The DWM service is enabled and running (the vulnerability only applies when DWM processes graphical objects)
-
Check for local unauthorized access vectorsReview user accounts on the system using 'net user' and verify that only trusted users have local administrator or authorized user permissionsAffected if Untrusted or unauthorized user accounts exist with local access rights, as the attacker requires local authorized access to exploit this flaw
You are affected if your Windows build number is within the affected version ranges AND the dwmcore.dll file version has not been updated to include the security fix.
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.14393.933910.0.17763.902010.0.19044.7548
Apply the relevant Microsoft security update for Windows DWM Core Library once released; until then, restrict local access to trusted users only and monitor for anomalous process behavior.
Windows 10 1607: 10.0.14393.9339 | Windows 10 1809: 10.0.17763.9020 | Windows 10 21h2: 10.0.19044.7548 | Windows 10 22h2: 10.0.19045.7548 | Windows 11 24h2: 10.0.26100.8875 | Windows 11 25h2: 10.0.26200.8875 | Windows 11 26h1: 10.0.28000.2525 | Windows Server 2016: 10.0.14393.9339
- Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Determine which Windows 10 or 11 version family applies to your system from the affected versions list
- Apply the appropriate Windows Update: For Windows 10 1607/Server 2016, upgrade to version 10.0.14393.9339 or later
- For Windows 10 1809, upgrade to version 10.0.17763.9020 or later
- For Windows 10 21h2, upgrade to version 10.0.19044.7548 or later
- For Windows 10 22h2, upgrade to version 10.0.19045.7548 or later
- For Windows 11 24h2, upgrade to version 10.0.26100.8875 or later
- For Windows 11 25h2, upgrade to version 10.0.26200.8875 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50437 — 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-50437 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