Quick answers
- Is CVE-2026-121412 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121412 being exploited in the wild.
- How severe is CVE-2026-121412?
- Medium severity, with a CVSS score of 6.5, published 3 November 2026.
- Which products and versions are affected?
- FreeRDP 3.0.0 to 3.31.1.
- Is there a fix for CVE-2026-121412?
- Yes: fixed in 3.32.2. Until then: Restrict which DVCs are selected for proxy interception, or disable DVC interception if not required. Implement per-session and per-process resource accounting and cumulative limits on message reassembly buffers until upstream patches are applied. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121412 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-121412?
- Check whether you run FreeRDP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.32.2
Restrict which DVCs are selected for proxy interception, or disable DVC interception if not required. Implement per-session and per-process resource accounting and cumulative limits on message reassembly buffers until upstream patches are applied.
Technical details
The vulnerability exists in DVC message reassembly within the FreeRDP proxy where no cumulative limit is enforced on reassembly buffers. An attacker can send a DATA_FIRST fragment with a large declared length and then send incomplete follow-up fragments, causing the proxy to retain unbounded heap memory proportional to traffic. This requires an established RDP session through the proxy and a DVC configured for interception.
Affected products
- FreeRDP FreeRDP 3.0.0 to 3.31.1
Timeline
- 2026-10-19: disclosed
- 2026-11-03: advisory