FreeRDP CVE-2026-121952: a malicious RDP server writes past the bitmap cache
FreeRDP CVE-2026-121952: a malicious RDP server writes past the bitmap cache
FreeRDP before 3.32.2 contains an out-of-bounds write tracked as CVE-2026-121952. The public advisory describes a malformed bitmap cache v2 capability set. The parser rejects only values above five numCellCaches, while later code accesses fixed cache indices from zero through four. A malicious RDP server can use the resulting mismatch to write outside the intended buffer in a connecting client.
This is a client-side memory-safety bug. The victim connects to an attacker-controlled or compromised RDP server, and the server supplies crafted capability data during the session. That changes the threat model from "is my RDP server exposed?" to "which clients connect to untrusted servers?"
The protocol is the input
RDP negotiates a set of capabilities before it draws the remote desktop. Bitmap cache v2 describes how the client and server will cache images. The parser reads a count from the server and allocates or indexes structures based on that count. If validation and use disagree, a value that is syntactically accepted can produce an unsafe access.
The important security principle is consistency. A count should be checked at the point where it is parsed and again where it is used. The same rule applies to an offset, a width, a height, or an array length. A check that rejects one invalid range does not prove that every lower bound and every subsequent access is safe.
The advisory says the proxy component is affected. It does not mean that every FreeRDP deployment exposes an RDP server to the internet. A user running xfreerdp, an embedded thin client, a remote-support agent, or an application that embeds FreeRDP may be a client. The server can be malicious even if it is not internet-facing.
Who connects where
Inventory every product that embeds FreeRDP. Include Linux desktops, thin clients, virtual desktop gateways, remote-support tools, kiosks, and custom applications. Record the shipped library version and the update mechanism. A distribution package may be behind the upstream release even when the application UI looks current.
Then map connection destinations. Users may connect to internal VDI brokers, managed cloud desktops, customer environments, or ad hoc servers. Review whether those destinations are authenticated and whether users can start a connection to an arbitrary host from a client application.
Review file types and links that can launch an RDP connection. A crafted .rdp file or URL handler can send a user to a malicious endpoint. The client still has to negotiate the vulnerable capability, but convenience features can make that less visible.
Patch the client
Upgrade FreeRDP to 3.32.2 or later. Because many products bundle the library, check the vendor's advisory as well. Rebuilding an application against the fixed library is different from updating a standalone package. Confirm the version used at runtime as well as the version listed in a build manifest.
After upgrading, test connections to a known-good RDP server. Confirm that bitmap cache negotiation succeeds and that malformed capability sets are rejected. Capture the client version, library build, and test date in the change record.
If a client connected to an untrusted server during the exposure window, treat the endpoint as potentially compromised. Memory corruption can be triggered without a visible prompt. Review process crashes, unusual child processes, persistence changes, and outbound connections. The advisory does not provide a universal exploitation signature, so endpoint evidence must be combined with connection history.
Reduce the untrusted server path
Use allowlists for RDP destinations where the workflow permits it. Disable or tightly control URL handlers that open arbitrary RDP targets. For support teams that connect to customer systems, provide a managed gateway and verify the server identity before the client negotiates desktop capabilities.
Segment clients so that a memory-safety failure in the RDP stack cannot immediately reach management credentials or file shares. Do not store privileged credentials in a client profile that can be used automatically against an unknown server.
The patch fixes the parser. The design change prevents a bad server from becoming a common path into an otherwise trusted endpoint.
References
- CVE-2026-121952 GitHub advisory
- VulnCheck advisory for FreeRDP
- FreeRDP security advisories
Mentions
FreeRDP CVE-2026-121952: a malicious RDP server writes past the bitmap cache FreeRDP CVE-2026-121952: a malicious RDP server writes past the bitmap cache FreeRDP before 3.32.2 contains an out-of-bounds write tracked as CVE-2026-121952. The public advisory describes a malformed bitmap cache v2 capability set. The parser rejects only values above five numCellCaches, while later code accesses fixed cache indices from zero through four. A malicious RDP server can use the resulting mismatch to write outside the intended buffer in a connecting client. This is a client-side memory-safety bug. The victim connects to an attacker-controlled or compromised RDP server, and the server supplies crafted capability data during the session. That changes the threat model from "is my RDP server exposed?" to "which clients connect to untrusted servers?" The protocol is the input RDP negotiates a set of capabilities before it draws the remote desktop. Bitmap cache v2 describes how the client and server will cache images. The parser reads a count from the server and allocates or indexes structures based on that count. If validation and use disagree, a value that is syntactically accepted can produce an unsafe access. The important security principle is consistency. A count should be checked at the point where it is parsed and again where it is used. The same rule applies to an offset, a width, a height, or an array length. A check that rejects one invalid range does not prove that every lower bound and every subsequent access is safe. The advisory says the proxy component is affected. It does not mean that every FreeRDP deployment exposes an RDP server to the internet. A user running xfreerdp, an embedded thin client, a remote-support agent, or an application that embeds FreeRDP may be a client. The server can be malicious even if it is not internet-facing. Who connects where Inventory every product that embeds FreeRDP. Include Linux desktops, thin clients, virtual desktop gateways, remote-support tools, kiosks, and custom applications. Record the shipped library version and the update mechanism. A distribution package may be behind the upstream release even when the application UI looks current. Then map connection destinations. Users may connect to internal VDI brokers, managed cloud desktops, customer environments, or ad hoc servers. Review whether those destinations are authenticated and whether users can start a connection to an arbitrary host from a client application. Review file types and links that can launch an RDP connection. A crafted .rdp file or URL handler can send a user to a malicious endpoint. The client still has to negotiate the vulnerable capability, but convenience features can make that less visible. Patch the client Upgrade FreeRDP to 3.32.2 or later. Because many products bundle the library, check the vendor's advisory as well. Rebuilding an application against the fixed library is different from updating a standalone package. Confirm the version used at runtime as well as the version listed in a build manifest. After upgrading, test connections to a known-good RDP server. Confirm that bitmap cache negotiation succeeds and that malformed capability sets are rejected. Capture the client version, library build, and test date in the change record. If a client connected to an untrusted server during the exposure window, treat the endpoint as potentially compromised. Memory corruption can be triggered without a visible prompt. Review process crashes, unusual child processes, persistence changes, and outbound connections. The advisory does not provide a universal exploitation signature, so endpoint evidence must be combined with connection history. Reduce the untrusted server path Use allowlists for RDP destinations where the workflow permits it. Disable or tightly control URL handlers that open arbitrary RDP targets. For support teams that connect to customer systems, provide a managed gateway and verify the server identity before the client negotiates desktop capabilities. Segment clients so that a memory-safety failure in the RDP stack cannot immediately reach management credentials or file shares. Do not store privileged credentials in a client profile that can be used automatically against an unknown server. The patch fixes the parser. The design change prevents a bad server from becoming a common path into an otherwise trusted endpoint. References - CVE-2026-121952 GitHub advisory - VulnCheck advisory for FreeRDP - FreeRDP security advisories
RDP、VNC、SSH 各装一个客户端，密码散着放，换台机器重配一遍。商业版还按人头收年费。 Remmina 一个客户端全收，连接存条目标签页切换，可调分辨率/多屏/剪贴板/传文件。 freerdp/remmina
FreeRDP ⭐ 14k FreeRDP is an open-source library that implements the Remote Desktop Protocol for developers building remote desktop clients and servers. 🔗 FreeRDP/FreeRDP #opensource t.co
gnome-remote-desktop / windows app Hi, since a few days ago windows app an Mac OS client stopped connecting to gnome-remote-desktop. It looks like an SSL handshake issue. kkRemote works fine from the same client. After the SSL aprovel windows app tries to connect and stops after a view minutes. Error code: 0x108 The gnome SSL certificate was updated 14 days ago, which fits the time that the connection stopped working. But not sure if its a dead end or a lead. server log: ERRCONNECT_CONNE... [RDP] Network or intentional disconnect, stopping session Could it be the same, similar issue? FreeRDP#13549 3.32.0 server sends Early User Authorization Result before TSCredentials - Windows App hangs after NLA (HYBRID_EX, regression from #13415) My Versions: - gnome-remote-desktop 50.2-0ubuntu0.1 - libfreerdp-server3-3 3.32.1+dfsg-0ubuntu0.26.04.1 - libfreerdp3-3 3.32.1+dfsg-0ubuntu0.26.04.1 - libwinpr3-3 3.32.1+dfsg-0ubuntu0.26.04.1
gnome-remote-desktop / windows app Hi, since a few days ago windows app an Mac OS client stopped connecting to gnome-remote-desktop. It looks like an SSL handshake issue. kkRemote works fine from the same client. After the SSL aprovel windows app tries to connect and stops after a view minutes. Error code: 0x108 The gnome SSL certificate was updated 14 days ago, which fits the time that the connection stopped working. But not sure if its a dead end. server log: ERRCONNECT_CONNE... [RDP] Network or intentional disconnect, stopping session Could it be the same, similar issue? FreeRDP#13549 3.32.0 server sends Early User Authorization Result before TSCredentials - Windows App hangs after NLA (HYBRID_EX, regression from #13415) My Versions: - gnome-remote-desktop 50.2-0ubuntu0.1 - libfreerdp-server3-3 3.32.1+dfsg-0ubuntu0.26.04.1 - libfreerdp3-3 3.32.1+dfsg-0ubuntu0.26.04.1 - libwinpr3-3 3.32.1+dfsg-0ubuntu0.26.04.1
@corndogjpn2 你有时间的话可以自己 Vibe 一个 freerdp/freerdp