CVE-2026-50330
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 Remote Desktop Client allows an unauthorized attacker to elevate privileges 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 confidenceA heap-based buffer overflow vulnerability in the Remote Desktop Client enables an unauthenticated attacker to gain elevated privileges through network-based exploitation. The critical severity (CVSS 9.8) indicates potential for complete system compromise. This is a memory corruption vulnerability in client-side code that can be triggered by a malicious RDP server or man-in-the-middle attack.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify your Windows version and build numberAffected if The Windows version matches one of the affected builds: Windows 10 1607 (build < 14393.9339), Windows 10 1809 (build < 17763.9020), Windows 10 21h2 (build < 19044.7548), Windows 10 22h2 (build < 19045.7548), Windows 11 24h2 (build < 26100.8875), Windows 11 25h2 (build < 26200.8875), Windows 11 26h1
-
Confirm Remote Desktop Client usageVerify that mstsc.exe (Remote Desktop Connection client) is present on the system by checking C:\Windows\System32\mstsc.exe or running 'where mstsc'Affected if The Remote Desktop Client (mstsc.exe) is installed on the system
-
Check RDP Client file versionRight-click mstsc.exe in System32, select Properties, then Details to view the File Version, or run 'wmic datafile where name="C:\\Windows\\System32\\mstsc.exe" get Version'Affected if The mstsc.exe version is lower than the patched version corresponding to your Windows build (this indicates an unpatched state)
-
Verify Windows Update patch statusOpen Settings > Windows Update > View update history and look for security updates related to Remote Desktop Client or CVE-2026-50330, or run 'powershell Get-HotFix | Where-Object {$_.Description -eq "Security Update"}' to list installed security patchesAffected if No security patch for CVE-2026-50330 appears in the installed updates
You are affected if your Windows version matches the affected version ranges AND the Remote Desktop Client is installed AND no corresponding security patch has been applied.
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 vendor-provided security patches for the Remote Desktop Client immediately. Until patched, restrict network access and verify RDP server authenticity to reduce attack surface.
Install the appropriate Microsoft security update for your Windows version from Windows Update or Microsoft Update Catalog (search for CVE-2026-50330)
- Identify the Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
- Open Windows Update by pressing Win+R, typing 'ms-settings:windowsupdate', and pressing Enter
- Click 'Check for updates' and install all available security updates
- For Windows Server 2012/R2, this version is past mainstream support; check for Extended Security Updates (ESU) or consider upgrading to a supported Windows Server version
- Verify the installed version matches or exceeds the fixed build: 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
- Restart the system if prompted to complete the patch installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50330 — 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-50330 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