On this page (7 sections)

FreeRDP, the open source Remote Desktop Protocol implementation, has a critical memory safety flaw in its proxy component. According to the NVD record, FreeRDP before 3.32.2 can be made to write out of bounds on the heap when a client connecting to the proxy declares fewer cell caches than the code expects.

If you run the FreeRDP proxy as a gateway in front of Windows or Linux desktops, or ship software that embeds it, this is worth acting on today. The fix is to move to 3.32.2 or later. At the time of writing, only one independent publisher covers the story, so details beyond the CVE record are limited.

What happened

The vulnerability was published on 2026-11-04. It affects the proxy part of FreeRDP, which sits between RDP clients and a backend server and relays the session. The flaw is in how the proxy reads the bitmap cache v2 capability set that a client announces while negotiating a session.

The CVE record references a GitHub advisory (GHSA-xc85-4mqc-xgcx) and a VulnCheck advisory, linked in the GitHub advisory and VulnCheck advisory references. The research available for this article contains only the NVD description, so we do not repeat claims beyond it.

Technical details in plain terms

During connection setup, an RDP client sends a Confirm Active message listing its capabilities. One of them says how many bitmap cache cells the client uses, in a field called numCellCaches. The function rdp_read_bitmap_cache_v2_capability_set checks this value, but only rejects numbers above 5.

The problem is that later code accesses the cell array at fixed positions 0 through 4. A client that declares fewer than five cell caches passes the check, yet the proxy still touches entries beyond what was declared. That is an out-of-bounds write on the heap, classified as CWE-787.

This is a common class of bug: a validation that checks one boundary (too many) but not the other (too few), while later code assumes a fixed size. Per the NVD description, the result can be heap corruption, heap data leaking to the backend server, or a crash.

Who is exposed

The flaw is in the proxy, so exposure depends on whether you use it. The attacker needs to be a client that can connect to the proxy, which means exposure grows if the proxy is reachable from the internet or from untrusted networks.

  • Teams running the FreeRDP proxy as an RDP gateway or broker in front of backend desktops or servers.
  • Hosting and VDI administrators who embed or package FreeRDP proxy builds.
  • Developers who vendor FreeRDP source and build the proxy themselves.
  • Less affected: people who only use a FreeRDP client to connect out. The NVD description refers specifically to the proxy.
The research does not state whether authentication is required before the vulnerable message is parsed. Treat any reachable proxy as potentially exposed until patched.

How to check your exposure

Start by finding out whether the proxy is deployed at all, and which version it is. The commands below are read-only. Which one applies depends on how FreeRDP was installed; package names vary by distribution, so confirm yours first.

Debian/Ubuntu: list installed FreeRDP-related packages and versions (read-only)Shell
dpkg -l | grep -i freerdp
RHEL and derivatives: list installed FreeRDP-related packages and versions (read-only)Shell
rpm -qa | grep -i freerdp
Look for a running FreeRDP proxy process (read-only); any output means a proxy may be activeShell
ps aux | grep -i freerdp | grep -v grep

Compare any version you find with 3.32.2. Distribution packages often backport fixes without changing the upstream version number, so also check your vendor's security notices. If you built FreeRDP from source or inside a container image, check the source tag or image build, since package managers will not list it.

What to do now

  1. Inventory every host, container image and appliance that includes the FreeRDP proxy.
  2. Upgrade FreeRDP to 3.32.2 or later, or install your distribution's patched package once it is available.
  3. Rebuild and redeploy container images and vendored builds that bundle an older FreeRDP.
  4. Until patched, restrict network access to the proxy to trusted networks, VPN users or known IP ranges.
  5. If the proxy is not needed, stop it and disable it.
  6. Review proxy logs for crashes or unexpected restarts since deployment, as a crash is one documented outcome.
  7. Check backend servers behind the proxy for unusual behavior, since the CVE notes heap data could leak to the backend.
Caution. Restarting or upgrading the proxy will drop active RDP sessions. Schedule the change in a maintenance window and tell users first.

On Debian or Ubuntu, this refreshes package lists and upgrades one installed FreeRDP package. Replace the placeholder with the package name from the earlier listing.

Debian/Ubuntu: refresh package lists and upgrade a FreeRDP package (package names vary, check the…Shell
sudo apt update && sudo apt install --only-upgrade <freerdp-package-name>

On RHEL and derivatives, this updates one installed FreeRDP package. Again, replace the placeholder with the name you found earlier.

RHEL and derivatives: update a FreeRDP package (package names vary, check the earlier listing)Shell
sudo dnf update <freerdp-package-name>

If your distribution has not yet shipped a fixed build, rely on the network restrictions above and watch for its advisory.

Detection and monitoring afterwards

Memory corruption bugs often show up first as instability. Watch for repeated crashes or restarts of the proxy process, and for connections from unfamiliar addresses just before them. Keep proxy logs long enough to look back over the period before you patched.

Because a proxy is an internet-facing service, it helps to know what your public surface looks like. A read-only scan of a site you verify can show what is reachable from outside, and monitoring can alert you to changes in certificates, DNS and headers. Neither one patches this flaw, so the upgrade still comes first.

What we do not know yet

  • The research does not report in-the-wild exploitation, and the CVE is not listed in CISA KEV.
  • No public exploit details are cited, and we do not describe any.
  • The content of the referenced advisories was not available to us, so treat the NVD wording as the confirmed baseline.
  • Whether code execution is possible is not stated. The CVE names heap corruption, data leakage to the backend and a crash.

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-121952: FreeRDP before 3.32.2 has an out-of-bounds write in the proxy because rdp_read_bitmap_cache_v2_capability_set rejects only numCellCaches values above 5, yet…nvd.nist.gov ·
  • FreeRDP
  • RDP
  • CVE-2026-121952
  • out-of-bounds write
  • patching