CVE-2026-55827

FreeRDP: Heap out-of-bounds write in RemoteFX (RFX) Cache Bitmap V3 decode

Published Jul 10, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.27.1, FreeRDP clients launched with the non-default /cache:codec:rfx option pass desktop stride and height to RemoteFX decoding for Cache Bitmap V3 data while allocating bitmap->data only for the smaller DstWidth and DstHeight in gdi_Bitmap_Decompress, allowing a malicious RDP server to trigger a heap out-of-bounds write with attacker-controlled offset and content. This issue is fixed in version 3.27.1.

Analysis

AI-generated

Technical impact

FreeRDP clients that enable RemoteFX decoding via the /cache:codec:rfx option allocate a bitmap data buffer based on the target destination width and height. A malicious Remote Desktop Protocol server can supply an RDP stream containing bitmap streams whose stride and height exceed the allocated destination size, causing a heap out‑of‑bounds write when the RemoteFX Cache Bitmap V3 decoder processes the data. This memory corruption can lead to overwrite of control data on the heap, potentially compromising data integrity and causing a denial of service by crashing the client application.

Affected Systems

The vulnerability affects FreeRDP clients distributed as FreeRDP prior to version 3.27.1. Users running any FreeRDP build older than 3.27.1 and employing RemoteFX decoding are at risk. No specific subsystem versions beyond the main client releases are listed.

Risk and Exploitability

The CVSS score of 7.5 indicates a medium‑to‑high severity. The EPSS score is less than 1% indicating a very low exploitation probability, and the absence of a KEV listing suggests that widespread exploitation has not yet been observed. An attacker would need to act as an RDP server to transmit a crafted RFX bitmap stream to the vulnerable client. The failure occurs on the client side, making the attack remote and likely to be triggered by any remote desktop connection that is not trusted.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade FreeRDP to version 3.27.1, which includes the out‑of‑bounds write fix.
  • Ensure that buffer sizes are validated before allocating memory (CWE‑131) and avoid using unvalidated external data for write operations (CWE‑787).
  • Disable RemoteFX on the client by removing the /cache:codec:rfx option or configuring the server to not use RemoteFX.
  • Limit inbound RDP connections to trusted hosts or monitor RDP traffic for malformed RemoteFX packets before allowing the connection.

Generated by OpenCVE AI on August 1, 2026 at 12:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8561-1 FreeRDP vulnerabilities
History
Type Values Removed Values Added
First Time appeared Freerdp
Freerdp freerdp
Vendors & Products Freerdp
Freerdp freerdp
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.27.1, FreeRDP clients launched with the non-default /cache:codec:rfx option pass desktop stride and height to RemoteFX decoding for Cache Bitmap V3 data while allocating bitmap->data only for the smaller DstWidth and DstHeight in gdi_Bitmap_Decompress, allowing a malicious RDP server to trigger a heap out-of-bounds write with attacker-controlled offset and content. This issue is fixed in version 3.27.1.
Title FreeRDP: Heap out-of-bounds write in RemoteFX (RFX) Cache Bitmap V3 decode
Weaknesses CWE-131
CWE-787
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-131

    Incorrect Calculation of Buffer Size

  • CWE-787

    Out-of-bounds Write

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 3:58 AM
Reserved
Jun 17, 2026, 4:29 PM
Status
Analyzed
Published
Jul 10, 2026, 8:16 PM
Modified
Jul 15, 2026, 5:17 AM
Severity
Important
Public date
Jul 10, 2026, 7:47 PM