CVE-2026-50347
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 · uneditedHeap-based buffer overflow in Windows Data dll allows an unauthorized attacker to execute code 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 confidenceHeap-based buffer overflow in a Windows Data DLL allows a local attacker to execute arbitrary code. The vulnerability occurs in heap memory allocation, where insufficient bounds checking permits overflowing allocated buffers.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 installed Windows 10 versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the full version numberAffected if Version is 10.0.14393.9338 or lower for 1607, 10.0.17763.9019 or lower for 1809, 10.0.19044.7547 or lower for 21h2, or 10.0.19045.7547 or lower for 22h2
-
Check installed Windows 11 versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the build numberAffected if Version is 10.0.26100.8874 or lower for 24h2, 10.0.26200.8874 or lower for 25h2, or 10.0.28000.2268/2524 or lower for 26h1
-
Check Windows Server 2012 versionRun 'winver' or check system properties to identify if the system is Windows Server 2012 or Server 2012 R2Affected if System is any Windows Server 2012 or Server 2012 R2 version (all versions affected)
-
Identify the vulnerable Windows Data DLLEnumerate DLLs named 'Windows.Data*' in system directories using 'Get-ChildItem -Path C:\Windows\System32\Windows.Data* -ErrorAction SilentlyContinue' or equivalent file listingAffected if The specific Windows Data DLL with the vulnerability is present (DLL name not specified in CVE data, compare to vendor advisory for exact file)
The system is affected if it runs any of the listed Windows versions below the specified build thresholds, or runs Windows Server 2012/2012 R2 of any build, AND the vulnerable Windows Data DLL is present on the system.
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 vendor-provided patches for the affected Windows Data DLL when released. Monitor vendor security advisories for patch availability.
- Consultation4.0 h
- Implementation1.0 h
- Testing8.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 $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50347 — 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-50347 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