CVE-2025-24035 is a remote code execution vulnerability in Windows Remote Desktop Services. The flaw is described as sensitive data storage in improperly locked memory. Available reporting indicates that an unauthenticated attacker can exploit the issue over the network, and that successful exploitation depends on winning a race condition. The vulnerability affects the Remote Desktop Services attack surface and can result in code execution on the target 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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical Windows Remote Desktop Services remote code execution vulnerability with CVSS 8.1 that Microsoft assesses as more likely to be exploited within 30 days.
Remote code execution vulnerability in Windows Remote Desktop Services due to sensitive data stored in improperly locked memory.
A Windows Remote Desktop Services remote code execution vulnerability listed in the summary table.
Remote code execution vulnerability in Windows Remote Desktop Services.
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.