FreeRDP versions before 3.28.0 contain a double-free vulnerability in the server-side rdpsnd channel handler. When processing a malformed Client Audio Formats PDU, rdpsnd_server_recv_formats can free the client-format allocation on an error path without clearing the corresponding context pointer and format-count state. Subsequent session teardown invokes rdpsnd_server_context_free, which frees the stale allocation again. The flaw can reliably terminate the FreeRDP server and may produce allocator-dependent heap corruption.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A FreeRDP server-side double-free vulnerability in handling malformed RDP Client Audio Formats PDUs. It can reliably terminate the server and may cause allocator-dependent heap corruption.
A FreeRDP-related vulnerability affecting Amazon Linux 2 FreeRDP and WinPR packages that can cause a high-impact availability loss. Exploitation requires network access and low privileges, with no user interaction required.
A vulnerability addressed by the Alma Linux ALSA-2026:61378 security update affecting FreeRDP/WinPR packages; no vulnerability-specific technical details are provided.
A vulnerability addressed by the referenced Oracle Linux FreeRDP update; no technical flaw details are provided.
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.