CVE-2026-27950
Heap-Use-After-Free in FreeRDP SDL2 Causes Potential Exploits
Publication date: 2026-02-25
Last updated on: 2026-02-27
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| freerdp | freerdp | to 3.23.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, prior to version 3.23.0. It is related to an incomplete fix for a heap-use-after-free issue originally described in CVE-2026-24680. Specifically, while the fix was applied to the SDL3 code path, the SDL2 implementation still contains the vulnerable logic because the pointer is not nulled after being freed. This means that in environments using SDL2, the vulnerability remains, potentially allowing use of freed memory.
How can this vulnerability impact me? :
The vulnerability can lead to use-after-free conditions in FreeRDP when using the SDL2 implementation. This can cause undefined behavior such as crashes or potentially allow an attacker to execute arbitrary code or cause denial of service by exploiting the freed memory. The CVSS base score of 5.5 indicates a moderate severity with network attack vector and no required privileges or user interaction.
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.23.0 or later, where the complete fix is applied.
If you are using builds or environments that still rely on the SDL2 implementation, ensure they are updated or switched to versions using SDL3 where the fix is present.