---
id: "CVE-2026-121388"
kind: "vulnerability"
aliases: ["CVE-2026-121388"]
title: "FreeRDP: malicious RDP server can exhaust client memory via dynamic channel"
severity: "high"
cvss: 7.1
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["freerdp", "linux", "package", "rdp", "remote-desktop", "windows"]
not_affected_if: ["no-freerdp-client", "version-3.32.2-or-later"]
published_at: "2026-11-03T15:17:25+00:00"
first_seen_at: "2026-11-03T15:21:57+00:00"
updated_at: "2026-11-03T15:23:07+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-121388", "first_seen_at": "2026-11-03T15:21:57+00:00"}]
---

# FreeRDP: malicious RDP server can exhaust client memory via dynamic channel

FreeRDP, a remote desktop client library, trusts a length field in DRDYNVC DATA_FIRST messages from the server and reserves up to about 4 GB before validating the body. A malicious RDP server can exhaust the memory of a connecting client, causing it to crash or stall.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the FreeRDP version in use, for example with `xfreerdp --version`, and see whether it is below `3.32.2`.
- Find applications or packages that bundle FreeRDP, such as remote desktop clients or libraries that link it.

## Fix

- Move FreeRDP to `3.32.2` or later.

## Timeline

- 2026-11-03T15:21:57+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-121388

## Documents

- [advisory] Vendor advisory: github.com https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-rrp5-666j-g6gp
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/freerdp-3.0.0-before-3.32.2-uncapped-memory-allocation-via-drdynvc-data-first

## From the sources

FreeRDP from 3.0.0 before 3.32.2 contains an uncontrolled resource allocation vulnerability that allows malicious RDP servers to force large client allocations through the DRDYNVC DATA_FIRST Length field. Attackers can declare lengths up to 4,294,967,295 bytes on running dynamic channels, causing StreamPool_Take to reserve memory before body validation and exhaust client memory.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_