Quick answers
- Is CVE-2026-121961 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121961 being exploited in the wild.
- How severe is CVE-2026-121961?
- Medium severity, with a CVSS score of 5.9, published 4 November 2026.
- Which products and versions are affected?
- FreeRDP Project FreeRDP before 3.32.2.
- Is there a fix for CVE-2026-121961?
- Yes: fixed in 3.32.2. Until then: Disable drdynvc channel interception in the proxy configuration or ensure the proxy does not explicitly set Intercept=drdynvc, as the vulnerability only manifests when dynamic channel interception is enabled. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121961 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-121961?
- Check whether you run FreeRDP Project 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
Disable drdynvc channel interception in the proxy configuration or ensure the proxy does not explicitly set Intercept=drdynvc, as the vulnerability only manifests when dynamic channel interception is enabled.
Technical details
A use-after-free vulnerability exists in the DRDYNVC channel tracker when the proxy intercepts dynamic virtual channels. An attacker-controlled target server sends duplicate CREATE_REQUEST_PDU messages for the same channel ID, racing against the front-end thread's DATA handling to trigger premature context freeing while borrowed pointers remain in use. The vulnerability manifests as a process crash (SIGSEGV in strlen or ASan abort); no code execution or information disclosure was demonstrated.
Affected products
- FreeRDP Project FreeRDP before 3.32.2
Timeline
- 2026-10-20: disclosed
- 2026-11-04: advisory