Skip to main content
VulnerabilityPublished

CVE-2026-121953: FreeRDP · Use After Free

Affects FreeRDPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 3.32.2 as a priority.

Data as of 4 Nov 2026, 15:58 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.09.3
CNA (VulnCheck)CVSS 3.19.8
Patch
Available – fixed in 3.32.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade FreeRDP and freerdp/FreeRDP to 3.32.2.

Affected software

ProductAffectedFixed in
FreeRDPFreeRDPAffected
  • <3.32.2
Fixed in
  • 3.32.2
GitHubfreerdp/FreeRDPpkg:github/freerdp/FreeRDPOther threatsAffected
  • <3.32.2
Fixed in
  • 3.32.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade FreeRDP to version 3.32.2 or later, where this use-after-free vulnerability is fixed. No other mitigation or workaround is indicated by the vendor advisory. Applying the official patch fully addresses the issue.

Description

CVE-2026-121953 is a critical use-after-free vulnerability in FreeRDP versions before 3.32.2. It occurs in the client's rdpgfx dynamic virtual channel when a duplicate-name channel with a new ChannelId overwrites the listener's callback slot, which is then freed without being cleared. A malicious RDP server can exploit this flaw by opening and closing such a channel and subsequently sending a PDU on the original channel, potentially causing a client crash or remote code execution.

References

Community reviews

Loading reviews…