Is CVE-2026-121955 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-121955 being exploited in the wild.

How severe is CVE-2026-121955?

High severity, with a CVSS score of 7.5, published 4 November 2026.

Is there a fix for CVE-2026-121955?

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-121955 attacked?

It is attacked over the network.

Am I affected by CVE-2026-121955?

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.

CVE-2026-121955: FreeRDP use-after-free in smartcard emulation ReleaseContext

CVE-2026-121955 · Severity: high · CVSS 7.5 · Published 2026-11-04

FreeRDP is a remote desktop client that supports smartcard emulation for authentication. A malicious remote server can trigger a use-after-free vulnerability by sending a sequence of smartcard commands, causing the client to crash or potentially execute arbitrary code. The vulnerability affects clients with smartcard emulation enabled.

Technologies: FreeRDP. Vendors: FreeRDP.

Quick answers

Is CVE-2026-121955 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-121955 being exploited in the wild.
How severe is CVE-2026-121955?: 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-121955?: 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-121955 attacked?: It is attacked over the network.
Am I affected by CVE-2026-121955?: 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 Emulate_SCardReleaseContext function frees the emulated SCardContext structure and its handle before the context's worker thread has been cancelled and joined, creating a race condition. An in-flight GETSTATUSCHANGE request continues reading from the freed memory after RELEASECONTEXT executes. A remote endpoint sending ESTABLISHCONTEXT followed by a long-timeout GETSTATUSCHANGE and then RELEASECONTEXT IRPs can trigger heap corruption or process crashes.

Affected products

FreeRDP FreeRDP before 3.32.2

Timeline

2026-10-20: disclosed
2026-11-04: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.