FreeRDP before 3.32.2 Use-After-Free via rdpgfx Dynamic Virtual Channel Close
FreeRDP clients before 3.32.2 that load the rdpgfx dynamic virtual channel (graphics pipeline enabled) are affected. Fixed in 3.32.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 3.32.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.32.2.
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed, CISA rates it automatable · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 50 if advisories confirm default setups are exposed
CVE-2026-121953 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) 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? →
- 45/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? →
- Unclear
- 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: poc
- Automatable: yes
- Technical impact: total
Summary
FreeRDP, the open-source Remote Desktop Protocol client library, is affected by a use-after-free flaw in its rdpgfx dynamic virtual channel handling. A malicious remote server can exploit it without logging in or any user action, crashing the client or potentially executing code on it.
Read the original description
FreeRDP before 3.32.2 has a use-after-free in the client's rdpgfx dynamic virtual channel: a duplicate-name channel with a new ChannelId overwrites the listener's single callback slot, which rdpgfx_on_close frees without clearing. A malicious RDP server can open and close such a channel, then send a PDU on the original channel to crash the client or potentially execute code.
What to do
Upgrade to a fixed version: 3.32.2.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- FreeRDP FreeRDP
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-121953
Is CVE-2026-121953 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The client frees heap memory tied to the rdpgfx dynamic virtual channel when the channel closes, then uses that memory again. This can crash the FreeRDP client and potentially lead to code execution.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-121953?
FreeRDP: before 3.32.2.Source: cve.now feed data
Am I affected, and how do I check?
FreeRDP versions before 3.32.2 are affected, but only clients that have the rdpgfx dynamic virtual channel loaded, meaning the graphics pipeline is enabled. To check, look at the installed FreeRDP version and whether the graphics pipeline is enabled in the client configuration.Source: github.com, vulncheck.com
How do I fix CVE-2026-121953?
Upgrade FreeRDP to version 3.32.2 or later. The facts list no workaround for this issue.Source: github.com, vulncheck.com