Client memory corruption via async stale-pointer dispatch
Published Aug 1, 2026 · Updated Aug 1, 2026
Heap use-after-free in FreeRDP before 3.29.0 allows remote attackers controlling an RDP server to corrupt client memory. The async update proxy shallow-copies RAIL window and notification-icon structures with nested parser-owned pointers, which are freed after callback return and later dispatched from the queue. AsyncUpdate must be enabled and the client must connect to a malicious or compromised RDP server; the bounded consequence is client memory corruption or a crash.
Summary
What happened
Heap use-after-free in FreeRDP before 3.29.0 allows remote attackers controlling an RDP server to corrupt client memory. The async update proxy shallow-copies RAIL window and notification-icon structures with nested parser-owned pointers, which are freed after callback return and later dispatched from the queue. AsyncUpdate must be enabled and the client must connect to a malicious or compromised RDP server; the bounded consequence is client memory corruption or a crash.
The record
- CVE
- CVE-2026-67300
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- FreeRDP
- Product
- FreeRDP
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.29.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo