FreeRDP 3.0.0 before 3.32.2 Uncapped Memory Allocation via DRDYNVC DATA_FIRST
FreeRDP 3.0.0 before 3.32.2 is affected when a client connects to a malicious or compromised RDP server with DRDYNVC negotiated. Fixed in 3.32.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.32.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The user connects to a malicious or compromised RDP server. DRDYNVC is negotiated. At least one dynamic channel has been created and is in DVC_CHANNEL_RUNNING state. The relevant build/plugin accepts the channel creation.
- Exploitation0/40No signal
- Exposure15/25Specific setups only, CISA rates it automatable
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
CVE-2026-121388 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects FreeRDP; fixed in 3.32.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.32.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
FreeRDP, a widely used open-source Remote Desktop Protocol client library, is affected. A malicious remote desktop server can exploit this flaw to make the client reserve huge amounts of memory, potentially exhausting the client's available memory and causing it to crash or become unresponsive.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
The user connects to a malicious or compromised RDP server. DRDYNVC is negotiated. At least one dynamic channel has been created and is in DVC_CHANNEL_RUNNING state. The relevant build/plugin accepts the channel creation.Upgrade to a fixed version: 3.32.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- FreeRDP FreeRDP
From 3.0.0 · fixed in 3.32.2
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121388
Is CVE-2026-121388 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A malicious or compromised RDP server can force the client to make very large memory allocations through the DRDYNVC DATA_FIRST Length field. This can exhaust the client's memory.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-121388?
FreeRDP: from 3.0.0 before 3.32.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 3.0.0 before 3.32.2 are in the affected range. The bug needs DRDYNVC to be negotiated, at least one dynamic channel in the running state, and a build or plugin that accepts the channel creation. Compare the installed FreeRDP version with that range to check a given install.Source: github.com, vulncheck.com
How do I fix CVE-2026-121388?
Upgrade FreeRDP to 3.32.2 or later.Source: github.com, vulncheck.com