Quick answers
- Is CVE-2026-121409 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121409 being exploited in the wild.
- How severe is CVE-2026-121409?
- Medium severity, with a CVSS score of 5.9, published 3 November 2026.
- Which products and versions are affected?
- FreeRDP before 3.32.2.
- Is there a fix for CVE-2026-121409?
- 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-121409 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-121409?
- 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
The vulnerability exists in nego_send_negotiation_request() which fails to properly validate that X.224 routing tokens fit within the one-byte length indicator before passing them to tpdu_write_header(), which asserts the length fits in UINT8_MAX. Attackers can trigger the assertion crash via an oversized LoadBalanceInfo in a Server Redirection PDU (client path) or by sending a 240–247 byte token directly to a FixedTarget freerdp-proxy (unauthenticated peer path). The impact is availability loss through process termination in assertion-enabled builds.
Affected products
- FreeRDP FreeRDP before 3.32.2
Timeline
- 2026-10-19: disclosed
- 2026-11-03: advisory