Quick answers
- Is CVE-2026-121388 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121388 being exploited in the wild.
- How severe is CVE-2026-121388?
- Medium severity, with a CVSS score of 6.5, published 3 November 2026.
- Which products and versions are affected?
- FreeRDP Project FreeRDP 3.0.0 through 3.32.1.
- Is there a fix for CVE-2026-121388?
- Yes: fixed in 3.32.2. Until then: Reject DRDYNVC DATA_FIRST messages declaring lengths above a conservative per-message limit before calling StreamPool_Take, and implement per-channel and per-session memory reservation budgets to cap total allocation across multiple dynamic channels. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121388 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-121388?
- Check whether you run FreeRDP Project FreeRDP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.32.2
Reject DRDYNVC DATA_FIRST messages declaring lengths above a conservative per-message limit before calling StreamPool_Take, and implement per-channel and per-session memory reservation budgets to cap total allocation across multiple dynamic channels.
Technical details
The DRDYNVC (Dynamic Virtual Channel) handler in FreeRDP accepts a 32-bit length field from the RDP server in DATA_FIRST PDUs and passes it directly to StreamPool_Take before validating the actual message body. StreamPool_Take preallocates the declared amount of memory via calloc even though subsequent fragments may never arrive or may be smaller, allowing an attacker to exhaust client address space. The vulnerability affects versions 3.0.0 through 3.32.1 and requires an established RDP connection with DRDYNVC negotiated and at least one dynamic channel active.
Affected products
- FreeRDP Project FreeRDP 3.0.0 through 3.32.1
Timeline
- 2026-10-19: disclosed
- 2026-11-03: advisory