Skip to main content
← Vulnerabilities

FreeRDP before 3.32.2 Denial of Service via RemoteFX RLGR decoder

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

7.1HighCNA
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 versions 3.11.0 through 3.32.1 are affected Client has RemoteFX surface decoding enabled Build has assertions enabled (WITH_VERBOSE_WINPR_ASSERT on); with the option disabled the conversion does not assert

19Pcve.now Index 19 of 100 · methodology v3 · provisional
  • 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
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active

CVE-2026-121394 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.

Published
Last modified
Published
Not listed in CISA KEV
19/100 · provisional
Specific setups only
Fix
Fixed in 3.32.2
None on Exploit-DB, Metasploit or GitHub

Summary

FreeRDP, a widely used open-source Remote Desktop Protocol client library, is affected by this flaw. A malicious RDP server can send specially crafted RemoteFX data that crashes the connecting client, causing a denial of service.

Read the original description

FreeRDP from 3.11.0 before 3.32.2 contains an assertion failure in the RemoteFX RLGR decoder that allows malicious servers to terminate clients. Attackers controlling an RDP server can send a RemoteFX tileset with RLGR code 32767, triggering a signed narrowing assertion in rfx_rlgr_decode and crashing the client.

What to do

  • Check whether your setup matches what the bug needs.

    FreeRDP versions 3.11.0 through 3.32.1 are affected Client has RemoteFX surface decoding enabled Build has assertions enabled (WITH_VERBOSE_WINPR_ASSERT on); with the option disabled the conversion does not assert
  • Upgrade to a fixed version: 3.32.2.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • FreeRDP FreeRDP

    From 3.11.0 · fixed in 3.32.2

Evidence 2

  1. Advisory
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121394

Is CVE-2026-121394 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 RDP server can crash the connected FreeRDP client process by sending data that triggers a failed assertion in the RemoteFX RLGR decoder. The advisory describes this as denial of service only, with no memory corruption, confidentiality, or integrity impact demonstrated.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-121394?

FreeRDP: from 3.11.0 before 3.32.2.Source: cve.now feed data

Am I affected, and how do I check?

FreeRDP versions 3.11.0 through 3.32.1 are affected. The bug needs a client with RemoteFX surface decoding enabled and a build with assertions on (WITH_VERBOSE_WINPR_ASSERT enabled, which is the default); the check the advisory points to is that build option and the client's RemoteFX setting.Source: github.com, vulncheck.com

How do I fix CVE-2026-121394?

Upgrade FreeRDP to version 3.32.2, which fixes the issue.Source: github.com, vulncheck.com