CVE-2026-67299
FreeRDP before 3.29.0 contains a client-side heap use-after-free in …
FreeRDP before 3.29.0 contains a client-side heap use-after-free in the async update message proxy for WINDOW_ICON_ORDER when AsyncUpdate is enabled (e.g. xfreerdp /async-update). In update_message_WindowIcon() a shallow CopyMemory() overwrites a freshly allocated lParam->iconInfo with the parser-owned windowIcon->iconInfo pointer. After the parser callback returns, update_recv_window_info_order() frees window_icon.iconInfo, but the queued async message still retains and later dispatches that stale pointer. A malicious or compromised RDP server sending a crafted RAIL Window Alternate Secondary Order with WINDOW_ORDER_ICON can trigger use-after-free, leading to memory corruption and client crash.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/FreeRDP/FreeRDP/commit/5370fb26fbf034ecd11d3026b6ad639b5fff493f
- github.com/FreeRDP/FreeRDP/security/advisories/GHSA-34hq-hwjw-q8v3
- www.vulncheck.com/advisories/freerdp-before-use-after-free-via-windowicon-async-message
- nvd.nist.gov/vuln/detail/CVE-2026-67299
- cve.org/CVERecord?id=CVE-2026-67299
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.