Skip to main content
← Vulnerabilities

FreeRDP 3.0.0 before 3.32.2 Proxy Memory Exhaustion via DVC Reassembly

Affects FreeRDP 3.0.0 up to 3.32.2 when a proxy configuration or loaded module intercepts an attacker-reachable DVC. Fixed in 3.32.2.

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. The DVC must be selected for proxy interception Proxy configuration or a loaded module must select the attacker-reachable DVC for interception The attacker must be able to establish an RDP session through the proxy

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • 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 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

CVE-2026-121412 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
15/100 · provisional
Specific setups only
Fix
Fixed in 3.32.2
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

FreeRDP from 3.0.0 before 3.32.2 contains an uncontrolled resource consumption vulnerability in the proxy that lets connected clients retain heap memory via intercepted DVC message reassembly. Attackers can declare a large DATA_FIRST length and keep sending fragments without completing the message, growing proxy memory proportional to traffic and degrading service.

What to do

  • Check whether your setup matches what the bug needs.

    The DVC must be selected for proxy interception Proxy configuration or a loaded module must select the attacker-reachable DVC for interception The attacker must be able to establish an RDP session through the proxy
  • Upgrade to a fixed version: 3.32.2.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • FreeRDP FreeRDP

    From 3.0.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-121412

Is CVE-2026-121412 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?

For a DVC selected for proxy interception, FreeRDP keeps a message incomplete while a connected client holds it open, so the shared proxy retains heap memory in proportion to traffic. This degrades the proxy's availability.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-121412?

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

Am I affected, and how do I check?

Versions from 3.0.0 before 3.32.2 are in scope. The setup also needs a proxy configuration or loaded module that selects the attacker-reachable DVC for interception, and an RDP session established through the proxy. Check the FreeRDP version and the proxy's DVC interception settings.Source: github.com, vulncheck.com

How do I fix CVE-2026-121412?

Upgrade to FreeRDP 3.32.2 or later, which contains the fix. The facts list no workaround.Source: github.com, vulncheck.com