CVE-2025-29967 is a critical heap-based buffer overflow vulnerability in Microsoft Remote Desktop Client. The flaw can be triggered when the client processes data from a remote desktop session controlled by an attacker, leading to memory corruption in the client process. Available reporting consistently characterizes the issue as a heap overflow and indicates exploitation occurs when a vulnerable Remote Desktop Client connects to an attacker-controlled RDP server. Successful exploitation can result in arbitrary code execution on the client system.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical remote code execution vulnerability in Windows Remote Desktop Services.
A past Microsoft vulnerability referenced only as part of vendor security history; no specific technical details are provided in the content.
Remote Desktop Client remote code execution vulnerability.
A remote code execution vulnerability in Remote Desktop Client & Gateway Service, allowing arbitrary code execution on client and server systems.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.