Windows 10 1607Operating system · Microsoft

CVE-2026-50504

HIGH · 7.5 CVSS v3.1 Published 2026-07-14

Fix available

A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click Patch available 5 weeks old

Official description

NVD · unedited

Buffer over-read in Remote Desktop Client allows an unauthorized attacker to disclose information over a network.

In the news

Third-party coverage

covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary

dbcve analysis · moderate confidence

A buffer over-read vulnerability in the Remote Desktop Client allows an unauthenticated remote attacker to read sensitive memory contents, potentially exposing session data, credentials, or other information transmitted during RDP sessions.

MitigationApply vendor-supplied patches to affected Remote Desktop Client installations. As an interim measure, restrict RDP connections to trusted networks and enforce Network Level Authentication (NLA) where possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Windows 10 1607Operating system

Affected:< 10.0.14393.9339

Windows 10 1809Operating system

Affected:< 10.0.17763.9020

Windows 10 21h2Operating system

Affected:< 10.0.19044.7548

Windows 10 22h2Operating system

Affected:< 10.0.19045.7548

Windows 11 24h2Operating system

Affected:< 10.0.26100.8875

Windows 11 25h2Operating system

Affected:< 10.0.26200.8875

Windows 11 26h1Operating system

Affected:< 10.0.28000.2525

Windows Server 2012Operating system

Affected:all versions= r2

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check Windows version to identify the release

Run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to determine the exact Windows version installed

Affected if The version falls within any of the affected ranges: Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 24h2, 25h2, 26h1 with build numbers below the specified thresholds, or Windows Server 2012/R2 (any version)
Verify Windows 10 build number

Run `winver` or `reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild` and compare the build number against the affected thresholds for your Windows 10 release

Affected if The build number is less than 14393.9339 (1607), 17763.9020 (1809), 19044.7548 (21h2), or 19045.7548 (22h2)
Verify Windows 11 build number

Run `winver` or `reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild` and compare against the affected thresholds

Affected if The build number is less than 26100.8875 (24h2), 26200.8875 (25h2), or 28000.2525 (26h1)
Check for Windows Server 2012/R2

Run `systeminfo | findstr /B /C:"OS Name"` to identify if the system is Windows Server 2012 or Windows Server 2012 R2

Affected if The system is running Windows Server 2012 or Windows Server 2012 R2 (all versions are affected)
Confirm RDP Client usage

Verify that the Remote Desktop Client (mstsc.exe) is actively used or installed by checking `where mstsc.exe` or reviewing recently used RDP connections

Affected if The RDP client is present and the system has established or may establish RDP connections to untrusted servers

The environment is affected if the system runs any Windows 10 version (1607, 1809, 21h2, 22h2) below the specified build thresholds, any Windows 11 version (24h2, 25h2, 26h1) below the specified build thresholds, or any version of Windows Server 2012/R2, AND the Remote Desktop Client is in use.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 10.0.14393.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later

Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548

Vendor patch msrc.microsoft.com →

Interim mitigation

Apply vendor-supplied patches to affected Remote Desktop Client installations. As an interim measure, restrict RDP connections to trusted networks and enforce Network Level Authentication (NLA) where possible.

Recommended fix High confidence

Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
For Windows 10 (1607, 1809, 21h2, 22h2): Navigate to Settings > Update & Security > Windows Update and check for updates, or manually download and install the specific KB update containing build 10.0.14393.9339 (1607), 10.0.17763.9020 (1809), 10.0.19044.7548 (21h2), or 10.0.19045.7548 (22h2)
For Windows 11 (24h2, 25h2, 26h1): Navigate to Settings > Windows Update and install updates to reach build 10.0.26100.8875 (24h2), 10.0.26200.8875 (25h2), or 10.0.28000.2525 (26h1)
For Windows Server 2012 R2: This version is end-of-life; contact Microsoft Support for Extended Security Updates (ESU) program eligibility, or migrate to a supported Windows Server version
After update installation, verify the new build number matches or exceeds the fixed version for your Windows release
Restart the system if prompted

Caveat Standard Windows update process; verify application compatibility after major version updates; Windows Server 2012 R2 requires paid ESU program or migration to newer server OS

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-50504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

msrc.microsoft.comPatch / commit
msrc.microsoft.comPatchVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50504 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-50504?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsUpgrade to 10.0.14393.9339 / 10.0.17763.9020 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.6%

Affects: Windows 10 1607

Remediation

A high-priority fix

Fix this in Windows 10 1607 18 hrs · Moderate

Typical engagement from $3,200

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-50504 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

In the news

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References