CVE-2026-23530: FreeRDP has heap-buffer-overflow in planar_decompress_plane_rle
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0,`freerdp_bitmap_decompress_planar` does not validate `nSrcWidth`/`nSrcHeight` against `planar->maxWidth`/`maxHeight` before RLE decode. 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 while processing compressed graphics data. The sources also note heap corruption risk, which could raise impact beyond denial of service depending on memory layout.
Executive priority
Treat as a high-priority client-side patching item where FreeRDP is used for remote administration. Urgency increases for teams connecting to third-party, lab, customer, or unmanaged RDP servers.
Technical view
The issue is a heap buffer overflow in planar RLE bitmap decompression. `freerdp_bitmap_decompress_planar` fails to validate source width and height against the planar context maximums before decode. A crafted server response can overrun heap memory in affected FreeRDP versions before 3.21.0.
Likely exposure
Exposure is primarily client-side: endpoints, jump boxes, automation, or applications using FreeRDP before 3.21.0, especially where users or tools connect to untrusted, attacker-controlled, or compromised RDP servers.
Exploitation context
The source bundle says KEV is false and provides no evidence of active exploitation. It describes malicious-server triggering and CVSS exploit maturity as proof-of-concept, but no safe public exploit details are included here.
Researcher notes
Focus validation on planar bitmap decompression bounds handling and package backports. The provided evidence supports crash and heap corruption risk, but does not prove reliable remote code execution or in-the-wild exploitation.
Mitigation direction
Upgrade FreeRDP to version 3.21.0 or later.
Apply relevant vendor packages, including Red Hat errata where applicable.
Avoid connecting vulnerable clients to untrusted or unknown RDP servers.
Check vendor guidance for distribution-specific fixed package versions.
Validation and detection
Inventory installed FreeRDP and libfreerdp package versions.
Confirm vulnerable systems are no longer running versions before 3.21.0.
Review RDP client use on workstations, jump hosts, and automation systems.
Verify Red Hat advisory applicability for managed Linux fleets.
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.