CVE-2026-24681
Analyzed Analyzed - Analysis Complete
Use-After-Free Vulnerability in FreeRDP URBDRC Channel Completion

Publication date: 2026-02-09

Last updated on: 2026-02-10

Assigner: GitHub, Inc.

Description
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.22.0, aAsynchronous bulk transfer completions can use a freed channel callback after URBDRC channel close, leading to a use after free in urb_write_completion. This vulnerability is fixed in 3.22.0.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-09
Last Modified
2026-02-10
Generated
2026-05-07
AI Q&A
2026-02-09
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
freerdp freerdp to 3.22.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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, asynchronous bulk transfer completions could use a freed channel callback after the URBDRC channel was closed. This leads to a use-after-free condition in the function urb_write_completion.

A use-after-free vulnerability occurs when a program continues to use memory after it has been freed, which can lead to undefined behavior, crashes, or potential exploitation.


How can this vulnerability impact me? :

The use-after-free vulnerability in FreeRDP can lead to serious security issues such as application crashes or potentially allow an attacker to execute arbitrary code or cause denial of service.

Given the CVSS v4.0 base score of 8.7, this vulnerability is considered high severity and can impact systems using vulnerable versions of FreeRDP by compromising their stability and security.


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 use after free issue in urb_write_completion has been fixed.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart