Quick answers
- Is CVE-2026-121956 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121956 being exploited in the wild.
- How severe is CVE-2026-121956?
- High severity, with a CVSS score of 7.5, published 4 November 2026.
- Which products and versions are affected?
- FreeRDP before 3.32.2.
- Is there a fix for CVE-2026-121956?
- 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-121956 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-121956?
- 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 double-free vulnerability exists in the retrieveSomeTgt function of WinPR's Kerberos SSPI implementation. When processing a user-to-user (u2u) TGT request with a server-name component containing '@', the function installs the krb5 default realm pointer into the principal structure without taking ownership, leading to the same memory being freed twice during cleanup. The attack is reachable before authentication via a GSS-wrapped NLA/CredSSP token and requires only network access and a specific Kerberos server configuration (keytab and default realm).
Affected products
- FreeRDP FreeRDP before 3.32.2
Timeline
- 2026-10-20: disclosed
- 2026-11-04: advisory