# Windows RDP Memory-Disclosure Vulnerabilities (CVE-2026-50445, CVE-2026-57982, CVE-2026-55003, CVE-2026-50497, CVE-2026-57979) — July 2026 Patch Tuesday

> Microsoft's July 14, 2026 Patch Tuesday fixed five Important-rated (CVSS 6.5) information-disclosure vulnerabilities in the Windows Remote Desktop Protocol (RDP) stack caused by buffer over-reads, out-of-bounds reads, an off-by-one error, and use of uninitialized resources. Successful exploitation lets a network-positioned attacker read process memory during an RDP session, potentially exposing credentials, session tokens, or ASLR-defeating pointers. Microsoft rates all five 'Exploitation Unlikely' and no public PoC or in-the-wild exploitation had been observed at disclosure.

- **Published:** 2026-07-15T00:00:00Z
- **Last reviewed:** 2026-07-15T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-1370
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-windows-rdp-memory-leak-cluster-tl-2026-1370.webp?v=d423fa50 (Threadlinqs threat intel: CVE-2026-50445 Windows RDP Leak: Detection & IOCs (TL-2026-1370) — Medium severity, 16 IOCs, 9 detection rules.)
- **ID:** TL-2026-1370
- **Severity:** MEDIUM (CVSS 6.5)
- **Category:** VULNERABILITY
- **Status:** PATCHED
- **Detections:** 9 (1 shown free below) · **IOCs:** 16
- **CVEs:** CVE-2026-50445, CVE-2026-57982, CVE-2026-55003, CVE-2026-50497, CVE-2026-57979

## Description

On July 14, 2026, as part of the largest Patch Tuesday release on record (569-621 CVEs across the ecosystem depending on tracker), Microsoft disclosed and patched five related but distinct information-disclosure vulnerabilities in the server-side Windows Remote Desktop Protocol implementation: CVE-2026-50445, CVE-2026-57982, CVE-2026-55003, CVE-2026-50497, and CVE-2026-57979. All five share an 'Important' severity rating, a CVSS 3.1 base score of 6.5 (temporal 5.7), a network attack vector, low attack complexity, and a High confidentiality / None integrity / None availability impact triad — meaning exploitation discloses data but does not modify state or cause denial of service.

The five CVEs cluster into two root-cause families. CVE-2026-50445 and CVE-2026-57979 are classic memory-safety over-reads: CVE-2026-50445 is a buffer over-read (CWE-126) in which the RDP protocol parser reads past an allocated buffer boundary and leaks adjacent heap memory to the remote peer; CVE-2026-57979 is an out-of-bounds read (CWE-125) with the same effect via a different code path in RDP session/channel data handling. CVE-2026-57982, CVE-2026-55003, and CVE-2026-50497 instead stem from failure to zero or initialize memory before it is used and transmitted: CVE-2026-57982 and CVE-2026-55003 are both 'Use of Uninitialized Resource' (CWE-908) findings, while CVE-2026-50497 is a compound off-by-one (CWE-193) plus uninitialized-resource (CWE-908) defect, where a boundary miscalculation causes one extra byte (or block) of stale heap content to be copied into an outbound RDP PDU.

Attack requirements differ slightly by CVE. CVE-2026-50445, CVE-2026-55003, CVE-2026-50497, and CVE-2026-57979 require no privileges (PR:N) but do require user interaction (UI:R) — the realistic scenario is a victim connecting to (or accepting a connection from) an attacker-controlled or attacker-manipulated RDP endpoint, e.g. a malicious RDP server the victim is lured into connecting to, or a machine-in-the-middle position that tampers with a legitimate RDP session. CVE-2026-57982 instead requires low privileges (PR:L) but no user interaction (UI:N), consistent with a scenario where a low-privileged authenticated session on the RDP host itself (or an already-established RDP session) is abused to read uninitialized server-side memory without further victim action.

Across all five, the practical impact is remote-memory disclosure: leaked heap contents can include in-memory credentials, session tokens/cookies, cryptographic key material, or pointers useful for defeating ASLR as a precursor to a follow-on exploit chain (the vulnerabilities themselves grant no code execution or privilege escalation). Microsoft's exploitability index rates all five 'Exploitation Unlikely' (some public trackers phrase this as 'less likely'), reflecting that reliable exploitation of a heap-layout-dependent info leak over the network is nontrivial to weaponize repeatably. No CVE in this set is CISA KEV-listed and no public proof-of-concept exploit code or evidence of in-the-wild exploitation had surfaced as of the July 14, 2026 disclosure and at time of this research — this negative finding was checked directly against CISA's KEV catalog feed and public exploit-code trackers cited in references.

The affected-version footprint is broad, spanning the full currently supported Windows client and server lifecycle: Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (24H2, 25H2, 26H1), and Windows Server 2012 through Windows Server 2025 (including 2012 R2, 2016, 2019, 2022, and Server Core installations where applicable), across 32-bit, x64, and ARM64 builds. Microsoft published fixed cumulative-update builds for each affected branch (e.g., Windows 10 1607/Server 2016 to build 14393.9339; Windows 10 1809/Server 2019 to 17763.9020; Windows 10 21H2 to 19044.7548; Windows 10 22H2 to 19045.7548; Windows 11 24H2/Server 2025 to 26100.8875; Windows 11 25H2 to 26200.8875; Windows 11 26H1 to 28000.2269) delivered via the standard July 2026 Patch Tuesday cumulative updates and the Microsoft Update Catalog. No documented workaround exists short of patching; Microsoft and third-party analysts recommend closing internet exposure of TCP/UDP 3389, fronting RDP with a VPN, Remote Desktop Gateway, or zero-trust proxy, enforcing Network Level Authentication (NLA), and prioritizing patch rollout to internet-facing hosts, administrative jump servers, and domain controllers.

This threat did not independently clear HUNT threat-selection thresholds (CVSS 6.5 sits below the 7.0 network-vector qualifying bar, exploitability is rated unlikely, there is no KEV listing, no public PoC, and no nation-state attribution or ransomware/supply-chain linkage) but is documented for RDP memory-disclosure exposure coverage given the size of the affected fleet and same-day patch availability.

## MITRE ATT&CK

- T1595 Active Scanning
- T1590 Gather Victim Network Information
- T1190 Exploit Public-Facing Application
- T1133 External Remote Services
- T1203 Exploitation for Client Execution
- T1212 Exploitation for Credential Access
- T1539 Steal Web Session Cookie
- T1552.006 Group Policy Preferences
- T1082 System Information Discovery
- T1046 Network Service Discovery
- T1005 Data from Local System
- T1021 Remote Services
- T1021.001 Remote Desktop Protocol
- T1557 Adversary-in-the-Middle
- T1686 Disable or Modify System Firewall

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Outbound RDP Client Connection to Unapproved External Host (Malicious RDP Server Lure)** (`TL-2026-1370-SPL-001`)

Detects mstsc.exe (or third-party RDP client) initiating an outbound RDP connection to a host outside the approved jump-server/RDGW allowlist -- the shared user-interaction precondition for CVE-2026-50445, CVE-2026-55003, CVE-2026-50497, and CVE-2026-57979, where a victim connects to an attacker-controlled or manipulated RDP endpoint that can trigger a client-side memory-disclosure read.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1595, T1590, T1133, T1203, T1021.001
- **Data sources:** sysmon, windows_security, edr_process_events
- **Severity:** medium
- **Confidence:** high

### Splunk SPL

```spl
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
| where match(lower(Image), "mstsc\.exe$") OR match(lower(Image), "(freerdp|rdesktop|mremoteng)")
| eval dest_host=coalesce(DestinationHostname, CommandLine)
| search NOT (CommandLine="*corp-jumpbox*" OR CommandLine="*approved-rdgw*")
| stats count min(_time) as first_seen max(_time) as last_seen values(CommandLine) as cmdlines by Computer, User, dest_host
| where count > 0
| table first_seen, last_seen, Computer, User, dest_host, cmdlines, count
```

### Microsoft KQL

```kql
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName in~ ("mstsc.exe", "freerdp.exe", "rdesktop.exe", "mRemoteNG.exe")
| where not(ProcessCommandLine has_any ("corp-jumpbox", "approved-rdgw"))
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessAccountName
| summarize ConnectCount=count(), FirstSeen=min(Timestamp), LastSeen=max(Timestamp) by DeviceName, AccountName, ProcessCommandLine
| order by LastSeen desc
```

### Sigma

```yaml
title: Outbound RDP Client Connection to Unapproved External Host
id: 7e1c2a3e-1370-4a10-9c3a-0f4a1370a001
status: experimental
description: Detects mstsc.exe or third-party RDP clients connecting to hosts outside the approved jump-server/RDGW allowlist, the lure precondition for the July 2026 RDP information-disclosure CVE cluster.
references:
    - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50445
    - https://cybersecuritynews.com/windows-remote-desktop-protocol-vulnerabilities-2/
author: Threadlinqs Team
date: 2026-07-15
tags:
    - attack.reconnaissance
    - attack.t1595
    - attack.initial_access
    - attack.t1133
    - attack.execution
    - attack.t1203
    - attack.lateral_movement
    - attack.t1021.001
    - cve.2026.50445
    - cve.2026.55003
    - cve.2026.50497
    - cve.2026.57979
logsource:
    product: windows
    category: process_creation
detection:
    selection:
        Image|endswith: '\mstsc.exe'
    filter_approved:
        CommandLine|contains:
            - 'corp-jumpbox'
            - 'approved-rdgw'
    condition: selection and not filter_approved
falsepositives:
    - Legitimate administrative RDP usage to unlisted but approved hosts
    - New jump servers not yet added to the allowlist
level: medium
```

**Known false positives:**

- Legitimate administrative RDP usage to a newly provisioned host not yet added to the jump-server/RDGW allowlist

**Tuning notes:** Maintain the approved jump-server/RDGW allowlist as a lookup table (SPL) or watchlist (KQL) instead of a hardcoded string match; expand the process-name list to cover site-specific RDP clients (e.g. Royal TS, Remote Desktop Manager).

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- RDP Listener Reachable From External Zone Without NLA (Exposure Precondition) (locked: unlock with TL Creds)
- Post-RDP-Session File and Registry Write Consistent With Collection of Disclosed Data (locked: unlock with TL Creds)
- Unpatched RDP Build Number Reachable on Domain Controller or Jump Server (locked: unlock with TL Creds)
- mstsc.exe Outbound Connection to Non-Allowlisted RDP Endpoint (locked: unlock with TL Creds)
- RDP Listener With Network Level Authentication Disabled (locked: unlock with TL Creds)
- Anomalous RDP Connection Volume Against Domain Controller or Jump Server (locked: unlock with TL Creds)
- Short-Lived Fixed-Size Read Following RDP Handshake (Memory-Disclosure Read/Response Shape) (locked: unlock with TL Creds)
- RDP Lateral Movement Using Recently-Established Session Following Disclosure-Pattern Connection (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Windows Remote Desktop Protocol Vulnerabilities](https://cybersecuritynews.com/windows-remote-desktop-protocol-vulnerabilities-2/)
- [Microsoft Patches Multiple Windows RDP Flaws That Expose Sensitive Data](https://cyberpress.org/microsoft-patches-multiple-windows-rdp-flaws/)
- [CVE-2026-50445: Patch Windows RDP Memory Disclosure Flaw](https://windowsforum.com/threads/cve-2026-50445-patch-windows-rdp-memory-disclosure-flaw.438479/)
- [CVE-2026-50445 - Security Update Guide - Microsoft](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50445)
- [CVE-2026-55003 - Security Update Guide - Microsoft](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55003)
- [CVE-2026-55003 Windows Remote Desktop Protocol (RDP) Information Disclosure Vulnerability](https://thewindowsupdate.com/2026/07/14/cve-2026-55003-windows-remote-desktop-protocol-rdp-information-disclosure-vulnerability/)
- [CVE-2026-57982 Technical Summary](https://cve.threatint.eu/CVE/CVE-2026-57982)
- [RDP Data Leak Flaw Fixed in July Windows Updates](https://windowsnews.ai/article/rdp-data-leak-flaw-fixed-in-july-windows-updates-heres-how-it-affects-you.438228)
- [CVE-2026-50445 - NVD](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-50445)
- [CISA Known Exploited Vulnerabilities Catalog](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json)
- [Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days](https://www.bleepingcomputer.com/news/microsoft/microsoft-july-2026-patch-tuesday-fixes-massive-570-flaws-3-zero-days/)
- [Patch Tuesday security updates for July 2026, the largest update ever. 621 CVEs in one month](https://securityaffairs.com/195347/security/patch-tuesday-security-updates-for-july-2026-the-largest-update-ever-621-cves-in-one-month.html)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-1370
