Quick answers
- Is CVE-2026-121963 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121963 being exploited in the wild.
- How severe is CVE-2026-121963?
- Medium severity, with a CVSS score of 5.9, published 4 November 2026.
- Which products and versions are affected?
- FreeRDP before 3.32.2.
- Is there a fix for CVE-2026-121963?
- Yes: fixed in 3.32.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121963 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-121963?
- 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
Technical details
A use-after-free exists in the asynchronous dynamic virtual channel handling for rdpsnd (audio). When a malicious RDP server sends an audio PDU and immediately closes the channel, the DATA callback queues a PDU while rdpsnd_on_close() frees the channel callback. The playback thread later dereferences the freed callback in rdpsnd_virtual_channel_write(), causing a crash. The vulnerability is in channels/rdpsnd/client/rdpsnd_main.c and requires precise DATA/CLOSE ordering via a race condition; no production trigger rate has been established.
Affected products
- FreeRDP FreeRDP before 3.32.2
Timeline
- 2026-10-20: disclosed
- 2026-11-04: advisory