CVE-2026-24680
Use-After-Free Vulnerability in FreeRDP SDL Pointer Component
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?
The vulnerability exists in FreeRDP, a free implementation of the Remote Desktop Protocol. Before version 3.22.0, there is a flaw in the sdl_Pointer_New function where it frees data on failure, and then pointer_free calls sdl_Pointer_Free which frees the same data again. This double free leads to a Use-After-Free (UAF) condition detected by AddressSanitizer (ASan).
How can this vulnerability impact me? :
This vulnerability can lead to a Use-After-Free condition, which may allow an attacker to execute arbitrary code, cause a crash, or trigger undefined behavior in the affected software. Since FreeRDP is used for remote desktop connections, exploitation could compromise the security and stability of remote sessions.
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, update FreeRDP to version 3.22.0 or later, where the issue has been fixed.