GHSA-983v-jp34-f3fm: FreeRDP before 3.32.2 Use-After-Free in Smartcard Emulation ReleaseContext

Published Nov 4, 2026

Updated

FreeRDP before 3.32.2 contains a use-after-free vulnerability in EmulateSCardReleaseContext that frees the emulated SCardContext before its worker thread is cancelled and joined. A malicious server can send ESTABLISHCONTEXT, a long-timeout GETSTATUSCHANGE, then RELEASECONTEXT smartcard IRPs to corrupt heap memory or crash clients using smartcard emulation.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade FreeRDP to a version that resolves this vulnerability.
Fixed in 3.32.2

Event History

Nov 4, 2026

CVE Published

via OSV·03:33 PM

Data Sourced

via OSV·03:33 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who is exposed to this issue?

Clients running FreeRDP versions before 3.32.2 that use smartcard emulation are exposed when connecting to a malicious server. The reported impact is heap-memory corruption or a client crash.

What does an attacker need to exploit it?

An attacker needs to operate or control a server that the vulnerable client connects to. The server sends ESTABLISHCONTEXT, a long-timeout GETSTATUSCHANGE, and RELEASECONTEXT smartcard IRPs in sequence; no client-side privileges or user interaction are indicated.

Is a default FreeRDP configuration affected?

The available information identifies smartcard emulation as the affected feature, but does not state whether it is enabled by default. Environments not using smartcard emulation are not identified as affected by this description.

What version addresses the issue?

Upgrade FreeRDP to version 3.32.2 or later. Versions before 3.32.2 are described as vulnerable.

GHSA-983v-jp34-f3fm: FreeRDP before 3.32.2 Use-After-Free in Smartcard Emulation ReleaseContext

Remediation

Event History

Frequently Asked Questions

Who is exposed to this issue?

What does an attacker need to exploit it?

Is a default FreeRDP configuration affected?

What version addresses the issue?

Company

Resources

Contact

Frequently Asked Questions

Who is exposed to this issue?

What does an attacker need to exploit it?

Is a default FreeRDP configuration affected?

What version addresses the issue?