Bug 2519818 (CVE-2026-55193) - CVE-2026-55193 FreeRDP: FreeRDP: Remote code execution or client crash via malicious TS Gateway
Summary: CVE-2026-55193 FreeRDP: FreeRDP: Remote code execution or client crash via ma...
Keywords:
Status: NEW
Alias: CVE-2026-55193
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2521923 2521925 2521927
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-19 17:56 UTC by OSIDB Bzimport
Modified: 2026-09-10 10:05 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:66347 0 None None None 2026-09-10 10:05:58 UTC
Red Hat Product Errata RHSA-2026:66349 0 None None None 2026-09-10 08:51:45 UTC

Description OSIDB Bzimport 2026-08-19 17:56:56 UTC 
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.27.0, FreeRDP clients using TS Gateway accept a server-controlled max_xmit_frag value in libfreerdp/core/gateway/rpc_bind.c without bounding it to the 4088-byte ReceiveFragment allocation. A malicious gateway can advertise 65535 and then send a response fragment of the same length, causing rpc_channel_read in libfreerdp/core/gateway/rpc.c to write up to 65535 bytes into the smaller ReceiveFragment buffer. This can crash the client and may permit code execution through attacker-controlled heap corruption. This issue is fixed in version 3.27.0.
Comment 2 errata-xmlrpc 2026-09-10 08:51:44 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:66349 https://access.redhat.com/errata/RHSA-2026:66349
Comment 3 errata-xmlrpc 2026-09-10 10:05:57 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:66347 https://access.redhat.com/errata/RHSA-2026:66347
Note You need to log in before you can comment on or make changes to this bug.