CVE-2026-24683
Use-After-Free in FreeRDP ainput_send_input_event Causes Crash
Publication date: 2026-02-09
Last updated on: 2026-02-10
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| freerdp | freerdp | to 3.22.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in FreeRDP, a free implementation of the Remote Desktop Protocol. The function ainput_send_input_event caches a channel_callback in a local variable and later uses it without proper synchronization. If a channel is closed concurrently, the callback may be freed or reinitialized while still in use, leading to a use-after-free condition.
This issue was present prior to version 3.22.0 and has been fixed in version 3.22.0.
How can this vulnerability impact me? :
The use-after-free vulnerability can lead to undefined behavior such as application crashes, memory corruption, or potentially arbitrary code execution. Because the vulnerability occurs without requiring privileges or user interaction, it can be exploited remotely, posing a high risk to affected systems.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade FreeRDP to version 3.22.0 or later, as the issue is fixed starting from that version.