Skip to main content
Mallory
High

Remote Desktop Client Heap-Based Buffer Overflow RCE

IdentifiersCVE-2026-42992CWE-122· Heap-based Buffer Overflow

CVE-2026-42992 is a critical remote code execution vulnerability in Microsoft Remote Desktop Client caused by a heap-based buffer overflow. The flaw is triggered in the client when it processes data from a Remote Desktop connection to a malicious or attacker-controlled Remote Desktop Server. Microsoft states that an unauthorized attacker can execute code over a network if a victim uses a vulnerable Remote Desktop Client to connect to the attacker-controlled server. The issue is classified as a heap-based buffer overflow in the client’s heap handling during RDP session processing.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote code execution on the victim machine running the vulnerable Remote Desktop Client. Because Microsoft rates confidentiality, integrity, and availability impact as high, exploitation could enable full compromise of the client context, including execution of arbitrary code, data theft or exposure, modification of system or user data, and disruption of system availability. The attack is client-side: the attacker gains code execution when the victim initiates a connection to the malicious Remote Desktop Server.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict use of vulnerable Remote Desktop Client instances so they do not connect to untrusted, internet-exposed, or attacker-controlled Remote Desktop Servers. Limit RDP client usage to trusted and controlled environments, enforce administrative policy around approved remote hosts, and reduce opportunities for users to initiate outbound RDP sessions to unknown systems. Network egress controls, jump-host usage, and user awareness measures can reduce exposure, but no specific vendor workaround is provided in the supplied content.

Remediation

Patch, then assume compromise.

Apply Microsoft’s June 2026 security update addressing CVE-2026-42992 and upgrade affected Remote Desktop Client installations to the vendor-fixed version. Prioritize patching systems that use Remote Desktop Client to connect to external, third-party, or otherwise untrusted RDP servers. Validate that all supported Windows systems and any redistributed or embedded Remote Desktop Client components receive the corresponding Microsoft fix.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows App Client For Windows Desktopapplication
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2025operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.