CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NHigh (8.7) in freerdp freerdp. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:HExplain CVE-2026-121955 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121955?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121955?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-121955 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| FreeRDP | before 3.32.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | freerdp2 | no fix listed | DEBIAN-CVE-2026-121955 |
| Debian | 13 | freerdp3 | no fix listed | DEBIAN-CVE-2026-121955 |
| Debian | 14 | freerdp3 | 3.32.2+dfsg-1 | DEBIAN-CVE-2026-121955 |
| Ubuntu | 16.04:LTS, 18.04:LTS | freerdp | no fix listed | UBUNTU-CVE-2026-121955 |
| Red Hat | enterprise_linux:10.2 | freerdp, libwinpr, freerdp-libs and 8 more | 2:3.32.2-1.el10_2 | RHSA-2026:94514 |
| Red Hat | enterprise_linux:10.3 | freerdp, libwinpr, freerdp-libs and 8 more | 2:3.32.2-1.el10_3 | RHSA-2026:98598 |
| AlmaLinux | 10 | freerdp, libwinpr, freerdp-libs and 3 more | 2:3.32.2-1.el10_2 | ALSA-2026:94514 |
| AlmaLinux | 10 | freerdp, libwinpr, freerdp-libs and 3 more | 2:3.32.2-1.el10_3 | ALSA-2026:98598 |
| Rocky Linux | 10 | freerdp, libwinpr, freerdp-libs and 8 more | 2:3.32.2-1.el10_2 | RLSA-2026:98598 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.
Red Hat rates this Important.
This vulnerability is rated as an Important severity because an untrusted RDP server can remotely cause application crashes or heap corruption without requiring elevated privileges. The flaw affects client sessions where smartcard device redirection and emulation are actively configured, which is not engaged during standard RDP connections. In typical environments where smartcard forwarding is unused, client systems remain unaffected by this issue.
Do not enable smartcard redirection when establishing FreeRDP sessions.
Ensure client connection profiles and command-line invocations omit the `/smartcard` parameter (for example, launch connections using `xfreerdp /v:<server_address>` without the `/smartcard` switch). In graphical connection managers or RDP configuration files, disable smartcard forwarding. Additionally, only establish RDP sessions to trusted endpoints.
Caveats: Omitting smartcard redirection prevents the use of smartcard hardware tokens and smartcard-based authentication within the remote session.
--- CME Mitigation Guidance (2026-11-06) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to cancel and join the background worker thread prior to freeing the emulated SCardContext in FreeRDP smartcard emulation: upgrade to FreeRDP 3.32.2+ (or the fixed Freerdp builds), which cancel and join the background worker thread before freeing the emulated SCardContext in Emulate_SCardReleaseContext, closing crafted sequence of smartcard IRPs containing ESTABLISHCONTEXT, long-timeout GETSTATUSCHANGE, and RELEASECONTEXT. Until patched, this is a concern on FreeRDP client sessions with smartcard redirection and smartcard emulation enabled, so Omit the /smartcard parameter from connection profiles and command-line invocations, disable smartcard forwarding in connection managers, and only establish RDP sessions to trusted endpoints. These controls limit blast radius and contain exploitation, but they do not fix the underlying use-after-free defect — apply the upstream patch to fully remediate.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | freerdp | Affected | |
| Red Hat Enterprise Linux 6 | freerdp | Not affected | |
| Red Hat Enterprise Linux 7 | freerdp | Affected | |
| Red Hat Enterprise Linux 8 | freerdp | Affected | |
| Red Hat Enterprise Linux 9 | freerdp | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-121955.