Skip to main content
VulnerabilityPublished

CVE-2026-121959: FreeRDP · Infinite Loop

Affects FreeRDPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 3.32.2 soon.

Data as of 4 Nov 2026, 15:58 UTC

CVSS 4.0 base score
7.1High
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.07.1
CNA (VulnCheck)CVSS 3.16.5
Patch
Available – fixed in 3.32.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/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 infinite loop vulnerability has been fixed. No other mitigation or workaround is indicated in the available data.

Description

CVE-2026-121959 is an infinite loop vulnerability in FreeRDP versions before 3.32.2. It occurs in the websocket_context_read function when a zero BIO result with payload outstanding is not properly handled. A malicious Remote Desktop Gateway can exploit this by sending a truncated WebSocket frame followed by a TLS close_notify, causing the client thread to enter a CPU-consuming spin loop until terminated.

References

Community reviews

Loading reviews…