CVE-2026-24684
Use-After-Free in FreeRDP RDPSND Component 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. Before version 3.22.0, the RDPSND async playback thread could process queued Protocol Data Units (PDUs) even after the communication channel was closed and its internal state was freed. This leads to a use-after-free condition in the function rdpsnd_treat_wave.
A use-after-free vulnerability occurs when a program continues to use memory after it has been freed, which can cause crashes or allow an attacker to execute arbitrary code.
This issue was fixed in FreeRDP version 3.22.0.
How can this vulnerability impact me? :
The use-after-free vulnerability in FreeRDP can lead to serious security impacts. Because the vulnerability involves accessing freed memory, it can potentially be exploited to execute arbitrary code, cause application crashes, or lead to denial of service.
Given the CVSS base score of 8.7, this vulnerability is considered high severity, indicating a significant risk if exploited.
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?
The vulnerability in FreeRDP is fixed in version 3.22.0. To mitigate this vulnerability, you should upgrade FreeRDP to version 3.22.0 or later.