Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Stand up malicious RDP server
  2. Delivery
    Lure user via phishing .rdp file
  3. Exploit
    Victim connects outbound to server
  4. Execution
    Server sends crafted RDP response
  5. Persist
    Trigger use-after-free in client heap
  6. Impact
    Execute code as logged-in user

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the victim to initiate an RDP session from the vulnerable Remote Desktop Client to an attacker-controlled or attacker-compromised RDP server - the CVSS UI:R bit confirms user interaction is mandatory, and PR:N confirms the attacker needs no prior credentials on the client. The attack is limited by this client-initiated direction: the attacker cannot reach out and exploit clients that are not actively connecting outbound to their server, so social engineering (malicious .rdp file, link, or rogue server impersonating a legitimate one) is the gating step. Unauthenticated network-side exploitation against listening services is not in scope; only the client-side parsing path is affected.

Impact

The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H decomposes to network-reachable, low-complexity, no privileges required, but user interaction required - the user must initiate or accept an RDP session to a malicious server. This is a real but conditional risk: there is no CISA KEV listing and no public POC referenced, and EPSS data was not provided, so this currently sits in the 'patch promptly' tier rather than emergency. The high-impact triad (C:H/I:H/A:H) combined with full code execution on workstations - frequently administrator endpoints used for lateral RDP into servers - elevates the practical risk in environments where jump hosts or admin workstations routinely make outbound RDP connections to untrusted networks.

Exploit ScenarioDerived

An attacker stands up a malicious RDP server and lures a target - for example, a system administrator - into connecting to it through a phishing email containing an .rdp file, a malicious shortcut on a compromised internal host, or a typosquatted hostname. Once the client establishes the RDP session, the server returns crafted protocol responses that trigger the use-after-free, corrupting the client's heap and executing attacker-supplied code in the user's security context. No public exploit is identified at time of analysis, but the bug class is well-understood and historically exploitable.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 09, 2026

Remote code execution in Microsoft Remote Desktop Client occurs when a user connects to an attacker-controlled RDP server, allowing the server to corrupt heap memory and execute arbitrary code on the client endpoint. The flaw carries a CVSS 8.8 (High) rating reflecting network reach with required user interaction, and no public exploit is identified at time of analysis. The attack pivots the traditional RDP threat model - attackers compromise clients that initiate outbound connections rather than exposed servers.

RemediationAI

Apply the Microsoft security update referenced in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47653 as soon as the patched build is identified for your platform - exact fix versions are not enumerated in the available data and must be pulled from MSRC. As a compensating control until patching completes, restrict outbound RDP (TCP/UDP 3389) from user workstations and admin jump hosts to only known-good internal RDP servers via host or perimeter firewall rules, which prevents users from connecting to attacker-controlled servers but breaks legitimate remote-to-external RDP use cases. Additionally, train administrators to avoid connecting to untrusted RDP endpoints and consider enforcing RDP connections only through gateways such as Remote Desktop Gateway with certificate validation.

Affected VersionsENISA

Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7417
Windows Server 2025 10.0.26100.0 <10.0.26100.32995
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26132
Windows Server 2022 10.0.20348.0 <10.0.20348.5256
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8880
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7417
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23228
Windows Server 2016 10.0.14393.0 <10.0.14393.9234
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9234
Windows Server 2019 10.0.17763.0 <10.0.17763.8880
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8655
Windows Server 2012 6.2.9200.0 <6.2.9200.26132
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.8880
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23228
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8655
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7219
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9234
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.32995

Affected Packages

microsoft windows_10_version_1607_10_0_14393_9234 fix: Windows 10 Version 1607 for 32-bit Systems 10.0.14393.9234, Windows 10 Version 1607 for x64-based Systems 10.0.14393.9234
microsoft windows_10_version_1809_10_0_17763_8880 fix: Windows 10 Version 1809 for 32-bit Systems 10.0.17763.8880, Windows 10 Version 1809 for x64-based Systems 10.0.17763.8880
microsoft windows_10_version_21h2_10_0_19044_7417 fix: Windows 10 Version 21H2 for 32-bit Systems 10.0.19044.7417, Windows 10 Version 21H2 for ARM64-based Systems 10.0.19044.7417, Windows 10 Version 21H2 for x64-based Systems 10.0.19044.7417
microsoft windows_10_version_22h2_10_0_19045_7417 fix: Windows 10 Version 22H2 for 32-bit Systems 10.0.19045.7417, Windows 10 Version 22H2 for ARM64-based Systems 10.0.19045.7417, Windows 10 Version 22H2 for x64-based Systems 10.0.19045.7417
microsoft windows_11_version_23h2_10_0_22631_7219 fix: Windows 11 Version 23H2 for ARM64-based Systems 10.0.22631.7219, Windows 11 Version 23H2 for x64-based Systems 10.0.22631.7219
microsoft windows_11_version_24h2_10_0_26100_8655 fix: Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.8655, Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8655
microsoft windows_11_version_25h2_10_0_26200_8655 fix: Windows 11 Version 25H2 for ARM64-based Systems 10.0.26200.8655, Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8655
microsoft windows_11_version_26h1_10_0_28000_2269 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2269, Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269
microsoft windows_server_2012_6_2_9200_26132 fix: Windows Server 2012 6.2.9200.26132, Windows Server 2012 (Server Core installation) 6.2.9200.26132
microsoft windows_server_2012_r2_6_3_9600_23228 fix: Windows Server 2012 R2 6.3.9600.23228, Windows Server 2012 R2 (Server Core installation) 6.3.9600.23228
microsoft windows_server_2016_10_0_14393_9234 fix: Windows Server 2016 10.0.14393.9234, Windows Server 2016 (Server Core installation) 10.0.14393.9234
microsoft windows_server_2019_10_0_17763_8880 fix: Windows Server 2019 10.0.17763.8880, Windows Server 2019 (Server Core installation) 10.0.17763.8880
microsoft windows_server_2022_10_0_20348_5256 fix: Windows Server 2022 10.0.20348.5256, Windows Server 2022 (Server Core installation) 10.0.20348.5256
microsoft windows_server_2025_10_0_26100_32995 fix: Windows Server 2025 10.0.26100.32995, Windows Server 2025 (Server Core installation) 10.0.26100.32995
euvd windows_10_version_1607 fix: 10.0.14393.9234
euvd windows_10_version_1809 fix: 10.0.17763.8880
euvd windows_10_version_21h2 fix: 10.0.19044.7417
euvd windows_10_version_22h2 fix: 10.0.19045.7417
euvd windows_11_version_23h2 fix: 10.0.22631.7219
euvd windows_11_version_24h2 fix: 10.0.26100.8655
euvd windows_11_version_25h2 fix: 10.0.26200.8655
euvd windows_11_version_26h1 fix: 10.0.28000.2269
euvd windows_server_2012 fix: 6.2.9200.26132
euvd windows_server_2012_r2 fix: 6.3.9600.23228
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23228
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26132
euvd windows_server_2016 fix: 10.0.14393.9234
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9234
euvd windows_server_2019 fix: 10.0.17763.8880
euvd windows_server_2019_server_core_installation fix: 10.0.17763.8880
euvd windows_server_2022 fix: 10.0.20348.5256
euvd windows_server_2025 fix: 10.0.26100.32995
euvd windows_server_2025_server_core_installation fix: 10.0.26100.32995

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 33 packages in microsoft, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability lives in Microsoft's Remote Desktop Client, the endpoint application implementing the Remote Desktop Protocol (RDP) for connecting to remote Windows hosts. The CWE-416 (Use After Free) classification, reinforced by the vendor's 'Heap-based buffer overflow' description and the Use After Free / Memory Corruption tags, indicates a memory safety defect where the client mishandles object lifetimes while parsing data returned from an RDP server. Freed heap objects are subsequently dereferenced, enabling an attacker controlling the server side of the RDP channel to corrupt adjacent heap structures and hijack control flow within the client process.

Know when Windows 10 1607 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CIRCL (temporal) 7.7 HIGH

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

1
Patch available
Jun 09, 2026 - 19:03 EUVD

DescriptionCVE.org

Heap-based buffer overflow in Remote Desktop Client allows an unauthorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

Microsoft Remote Desktop Client contains a remote code execution vulnerability (CVSS 8.8) triggered when organizational users connect to attacker-controlled RDP servers, directly compromising employee endpoints. This reverses the traditional RDP threat model-endpoints are exposed through outbound connections rather than inbound server exposure. No public exploit code has been identified at time of analysis, but the high severity rating combined with broad user exposure across the organization requires immediate action to restrict RDP client usage.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Firewall/proxy enforcement restricting outbound RDP connections to whitelisted internal servers only; (2) Require VPN authentication before permitting RDP client usage; (3) Disable Microsoft Remote Desktop Client on endpoints where operationally unnecessary; (4) Deploy endpoint detection and response (EDR) to monitor for suspicious RDP-related process behavior and memory corruption indicators; (5) Enforce least-privilege access controls for accounts authorized to use RDP; (6) Conduct user security awareness training on connecting only to authorized internal RDP servers.

Threat Intelligence Overview

EPSS Score
0.1%
Top 77% exploitable
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Unlikely
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Related Vulnerabilities in Remote Desktop Client Heap Overflow Code Execution

View all 3
CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy