FreeRDP before 3.32.2 Use-After-Free via dyn-channel-dump Module
Only affects freerdp-proxy configured with the shipped dyn-channel-dump module in FreeRDP 3.32.1 and earlier. 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. freerdp-proxy is configured with the shipped dyn-channel-dump module The dyn-channel-dump module is explicitly loaded and configured for the dynamic channel Affects FreeRDP 3.32.1 and earlier, where the relevant code is unchanged in 3.32.0 and 3.32.1
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
CVE-2026-121398 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (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? →
- 20/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
Summary
FreeRDP, an open-source Remote Desktop Protocol library, is affected through its freerdp-proxy dyn-channel-dump module. A malicious RDP server can exploit a timing flaw during session shutdown to crash the proxy process.
Read the original description
FreeRDP before 3.32.2 contains a cross-thread use-after-free vulnerability in the freerdp-proxy dyn-channel-dump module during session teardown. A malicious RDP target can send dynamic channel data while the front client disconnects, letting the client thread read freed ChannelData and crash the proxy process.
What to do
Check whether your setup matches what the bug needs.
freerdp-proxy is configured with the shipped dyn-channel-dump module The dyn-channel-dump module is explicitly loaded and configured for the dynamic channel Affects FreeRDP 3.32.1 and earlier, where the relevant code is unchanged in 3.32.0 and 3.32.1Upgrade to a fixed version: 3.32.2.
Timeline
- CVE published
- First seen by cve.now
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-121398
Is CVE-2026-121398 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?
The bug is a use-after-free memory-safety failure in the freerdp-proxy process, which can crash it. Code execution and information disclosure were not demonstrated.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-121398?
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 in scope, including 3.32.0 and 3.32.1, where the relevant code is unchanged. It only applies when freerdp-proxy has the shipped dyn-channel-dump module explicitly loaded and configured for the dynamic channel. Check the installed FreeRDP version and the freerdp-proxy configuration for dyn-channel-dump to see whether this setup is in use.Source: github.com, vulncheck.com
How do I fix CVE-2026-121398?
Upgrade FreeRDP to 3.32.2 or later, which contains the fix.Source: github.com, vulncheck.com