On this page (6 sections)

FreeRDP, an open source implementation of the Remote Desktop Protocol, has a critical memory-safety flaw in its client. According to the NVD record for CVE-2026-121953, versions before 3.32.2 contain a use-after-free in the rdpgfx dynamic virtual channel. A malicious RDP server can use it to crash the client or potentially execute code.

This matters to anyone who connects to RDP servers they do not fully control, and to developers and administrators who ship or run FreeRDP-based tools. Only one independent publisher covers this story so far, and the technical details in this article come solely from the NVD record.

What happened

The flaw was published on 2026-11-04. The NVD description says the bug lives in the client's handling of the rdpgfx dynamic virtual channel. The CVE record also lists two references: the FreeRDP project's GitHub security advisory GHSA-6wqx-rv3q-vcxp and a VulnCheck advisory page. This article does not draw on their contents, so read them directly for anything beyond the NVD description.

The direction of the attack is worth noting. This is not an attack on an RDP server. According to the description, the server is the attacker, and the victim is the client that connects to it.

Technical details in plain terms

A use-after-free happens when a program releases a piece of memory but keeps a pointer to it, then uses that pointer later. What the memory contains at that moment may be influenced by someone else, which can lead to crashes or, in some cases, code execution.

Per the CVE description, the sequence is as follows:

  • The listener for the channel keeps a single callback slot.
  • A channel opened with a duplicate name but a new ChannelId overwrites that slot.
  • When that channel closes, the rdpgfx_on_close handler frees the callback without clearing the pointer.
  • If the server then sends a PDU on the original channel, the client uses the freed memory.

The result, according to the record, is a client crash or potentially code execution. Whether reliable code execution is achievable in practice is not established by the research; the word the record uses is "potentially". No exploit details are given here, and none are needed to patch.

Who is affected

Per the CVE description, the affected component is the FreeRDP client before 3.32.2, and the attacker needs to be a malicious RDP server that the client connects to. In practical terms, exposure is most likely for:

  • Administrators and support staff who connect to customer or third-party machines.
  • Anyone who connects to RDP hosts they do not own or fully trust.
  • Developers and vendors who embed FreeRDP in remote-access tools, jump hosts or automation. The research does not list specific downstream products, so check what your own software bundles.

The research does not describe any risk to machines that only accept inbound RDP connections. A machine that also runs a vulnerable FreeRDP client, however, is exposed when it connects out.

How to check your exposure

Start by finding out which FreeRDP version is installed. The commands below are read-only. Package and binary names differ by distribution and build, so confirm what your system calls them before relying on the output.

Print the FreeRDP client version: run where the client is installed and look for a version below…Shell
xfreerdp --version
List installed FreeRDP packages and their versions (Debian/Ubuntu); look for versions below 3.32.2Shell
dpkg -l | grep -i freerdp
List installed FreeRDP packages and their versions (RHEL, Fedora and similar); look for versions…Shell
rpm -qa | grep -i freerdp
Distributions often backport fixes without changing the upstream version number. If your package shows an older version, check your distribution's security tracker for CVE-2026-121953 before concluding you are vulnerable or safe.

Also look for applications that bundle their own copy of FreeRDP, such as remote-desktop tools or containers. These will not show up in the system package list and need an update from their own vendor.

What to do now

The fix is in FreeRDP 3.32.2. No workaround is given in the research, so updating is the answer.

  1. Update FreeRDP to 3.32.2 or later, or install your distribution's patched package.
  2. Rebuild and redeploy any software or container images that bundle FreeRDP.
  3. Until updated, connect only to RDP servers you own or fully trust.
  4. Check your distribution's security tracker for the status of CVE-2026-121953.
  5. Ask vendors of remote-access tools whether they embed FreeRDP and when a fixed build ships.
Caution. Updating a package used by remote-access tooling can interrupt active sessions. Close open RDP sessions and schedule the update outside working hours for shared jump hosts.
Upgrade only the FreeRDP packages (Debian/Ubuntu); replace the placeholder with the package name…Shell
sudo apt update
sudo apt install --only-upgrade <freerdp-package-name>
Upgrade FreeRDP packages (RHEL, Fedora and similar); replace the placeholder with the package name…Shell
sudo dnf upgrade <freerdp-package-name>

Detection and monitoring

The research does not describe any indicators of compromise or known attacks. The description implies a client crash as one possible outcome, so unexplained FreeRDP client crashes right after connecting are worth investigating, especially against an unfamiliar host.

  • Review which hosts your administrators connect to and flag unfamiliar ones.
  • Watch your package manager or software inventory to confirm every machine reaches 3.32.2 or a patched distribution build.
  • Treat a workstation that crashed during an RDP session to an untrusted server as potentially affected, and follow your incident process.

If you also run public websites, certificate and DNS monitoring and a free SSL certificate checker can help you notice unexpected changes on your own domains. They do not address this FreeRDP bug. For broader habits, see our small business website security guide.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-121953: FreeRDP before 3.32.2 has a use-after-free in the client's rdpgfx dynamic virtual channel: a duplicate-name channel with a new ChannelId overwrites the…nvd.nist.gov ·
  • FreeRDP
  • RDP
  • use-after-free
  • CVE-2026-121953
  • patching