CVE-2026-23534: FreeRDP has heap-buffer-overflow in clear_decompress_bands_data
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0, a client-side heap buffer overflow occurs in the ClearCodec bands decode path when crafted band coordinates allow writes past the end of the destination surface buffer. A malicious server can trigger a client‑side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code‑execution risk depending on allocator behavior and surrounding heap layout. Version 3.21.0 contains a patch for the issue.
Security readout for executives and security teams
Plain-English summary
FreeRDP clients before 3.21.0 can be crashed by a malicious RDP server using crafted ClearCodec band data. The source describes potential heap corruption and code-execution risk, but does not prove reliable code execution or active exploitation.
Executive priority
Treat as high priority for environments using FreeRDP clients. Patch promptly, with extra urgency for teams connecting to external RDP services, because the client can be attacked by the server it connects to.
Technical view
The issue is a client-side CWE-122 heap buffer overflow in FreeRDP's clear_decompress_bands_data ClearCodec bands decode path. Crafted band coordinates can write past the destination surface buffer. FreeRDP 3.21.0 contains the upstream patch.
Likely exposure
Organizations using FreeRDP client builds older than 3.21.0 are exposed, especially where users connect to untrusted, internet-hosted, or compromised RDP servers. Red Hat references indicate downstream package tracking and advisories exist.
Exploitation context
The bundle says a malicious server can trigger the overflow remotely without privileges. KEV is false, and the provided sources do not show active exploitation. The stated impact is crash, heap corruption, and possible code execution depending on heap conditions.
Researcher notes
Focus review on ClearCodec band coordinate validation and destination surface bounds. The public bundle identifies the affected path and patched release, but does not provide complete exploit reliability, downstream package scope, or evidence of exploitation.
Mitigation direction
Upgrade FreeRDP to version 3.21.0 or later.
Apply relevant vendor security updates for packaged FreeRDP builds.
Prioritize clients that connect to untrusted or external RDP servers.
Limit FreeRDP use to trusted RDP endpoints until patched.
Check Red Hat or distribution guidance for affected package status.
Validation and detection
Inventory installed FreeRDP versions across workstations, jump hosts, and automation images.
Confirm deployed packages include the FreeRDP 3.21.0 fix or vendor backport.
Identify users or systems connecting to third-party or internet-facing RDP servers.
Review vulnerability scanner results against vendor advisory status.
Track Red Hat errata where FreeRDP is supplied by Red Hat.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.