CVE-2026-50376
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 of uninitialized resource in Windows RDP allows an unauthorized attacker to disclose information over a network.
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 confidenceThis vulnerability involves the use of an uninitialized resource in Windows Remote Desktop Protocol (RDP). When RDP processes certain operations, it fails to properly initialize memory or other resources before using them, allowing an unauthorized attacker on the network to read sensitive information from uninitialized memory pages that may contain residual data from previous operations.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Verify RDP is enabled on the systemOpen System Properties, look at the Remote tab, or check the registry key HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server for the value fDenyTSConnections (0 means enabled).Affected if RDP is enabled (fDenyTSConnections is set to 0)
-
Confirm the installed Windows version and build numberRun 'winver' from the command prompt or check System Information (msinfo32) to identify the exact Windows version and build number.Affected if The build number falls below the safe thresholds listed for the affected version
-
Compare your build against affected Windows 10 1607 rangeIf running Windows 10 version 1607, verify the build is below 10.0.14393.9339Affected if Build is below 10.0.14393.9339 on Windows 10 1607
-
Compare your build against affected Windows 10 1809 rangeIf running Windows 10 version 1809, verify the build is below 10.0.17763.9020Affected if Build is below 10.0.17763.9020 on Windows 10 1809
-
Compare your build against affected Windows 10 21h2 and 22h2 rangesIf running Windows 10 21h2 or 22h2, verify the build is below 10.0.19044.7548 (21h2) or 10.0.19045.7548 (22h2)Affected if Build is below 10.0.19044.7548 (21h2) or 10.0.19045.7548 (22h2)
-
Compare your build against affected Windows 11 rangesIf running Windows 11, identify the specific version (24h2, 25h2, or 26h1) and check if the build is below the respective threshold (10.0.26100.8875, 10.0.26200.8875, or 10.0.28000.2269/2525)Affected if Build is below the threshold for the installed Windows 11 version
A system is affected if RDP is enabled and the Windows version/build falls within any of the vulnerable ranges listed, or if it is any version of Windows Server 2012/R2 with RDP enabled.
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 Microsoft security patches for Windows systems with RDP enabled, and if immediate patching is not feasible, restrict network access to RDP ports (3389) or disable RDP on systems that do not require remote access.
Windows 10 1607: upgrade to 10.0.14393.9339 or later | Windows 10 1809: upgrade to 10.0.17763.9020 or later | Windows 10 21h2: upgrade to 10.0.19044.7548 or later | Windows 10 22h2: upgrade to 10.0.19045.7548 or later | Windows 11 24h2: upgrade to 10.0.26100.8875 or later | Windows 11 25h2: upgrade
- Identify the installed Windows version by running 'winver' or 'systeminfo' in Command Prompt
- For Windows 10 (1607, 1809, 21h2, 22h2): Navigate to Settings > Update & Security > Windows Update and install all available updates until the build number matches or exceeds the fixed version for your release
- For Windows 11 (24h2, 25h2, 26h1): Use Windows Update to install cumulative updates until reaching build 10.0.28000.2525 or higher
- For Windows Server 2012/2012 R2: Contact Microsoft Support for Extended Security Updates (ESU) as standard support has ended; alternatively, prioritize migrating to a supported Windows Server version
- Verify successful patching by checking the build number with 'winver'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50376 — 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-50376 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