A remote code execution vulnerability in Windows Remote Desktop Services affects systems configured with the Remote Desktop Gateway role. The issue is associated with a race condition that can lead to a use-after-free condition during processing within the RDS licensing or Remote Desktop Services code path. By connecting to a vulnerable target and triggering the timing flaw, an attacker may corrupt memory and execute arbitrary code on the affected system. The vulnerability is rated Critical with a CVSS score of 8.1.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code execution vulnerability in Windows Remote Desktop Services (RDS) that can be exploited via the Remote Desktop Gateway role, potentially through a use-after-free scenario.
Remote code execution vulnerability in Windows Remote Desktop Services caused by improper type evaluation; exploitable against systems configured as Remote Desktop Gateway and requiring a race condition win.
A 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.