Heap-Based Buffer Overflow in the EGFX Channel of neutrinolabs xrdp May Enable Remote Code Execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-35512?

CVE-2026-35512 is a vulnerability classified as Heap-based Buffer Overflow, affecting xrdp (affected versions: < 0.10.6). This vulnerability is rated High, with a CVSS score of 8.7. Current sources do not report this vulnerability as exploited.

Overview

Original source data

xrdp is an open source RDP server. Versions through 0.10.5 have a heap-based buffer overflow in the EGFX (graphics dynamic virtual channel) implementation due to insufficient validation of client-controlled size parameters, allowing an out-of-bounds write via crafted PDUs. Pre-authentication exploitation can crash the process, while post-authentication exploitation may achieve remote code execution. This issue has been fixed in version 0.10.6. If users are unable to immediately update, they should run xrdp as a non-privileged user (default since 0.10.2) to limit the impact of successful exploitation.

Affected products and scope

  • xrdp versions < 0.10.6 are declared affected.
  • The vendor advisory identifies 0.10.6 as the patched version.
  • The advisory describes the vulnerable component as the EGFX implementation and states that the flaw is reachable both before and after authentication.
  • The available record and advisory do not confirm the status of every parallel release branch outside the declared range. A vendor discussion states that v0.9.x is end-of-life and is not receiving vulnerability fixes, but that evidence is not sufficient to determine whether this specific issue affects that branch.

Technical details

neutrinolabs xrdp has a flaw in its EGFX implementation, the graphics dynamic virtual channel used to process graphics data in an RDP session. The component does not adequately validate client-controlled size parameters while processing crafted PDUs. This can cause data to be written beyond the bounds of a heap allocation, producing a heap-based buffer overflow and out-of-bounds write.

The flaw is reachable over the network through the RDP service and the supplied record indicates that no additional user interaction is required. Pre-authentication exploitation can crash the xrdp process. Post-authentication exploitation may achieve remote code execution and typically involves hijacking specific processes after successful user authentication. The available evidence does not identify the exact field, allocation path, or internal condition used to control the out-of-bounds write.

Exploitability

  • Reachability: A remote attacker can target xrdp over the network by sending crafted RDP PDUs.
  • Authentication and interaction: Pre-authentication exploitation can crash the process. Remote code execution is generally associated with post-authentication exploitation and successful user authentication; no additional user interaction is required.
  • Complexity: The advisory describes low attack complexity, and the record describes low required privileges.
  • Exploit status: The supplied record marks public_exploit as false and leaves known_exploited unset. This does not establish that exploitation has not occurred in the wild.

Technical impact

The flaw permits an out-of-bounds write on the heap within the xrdp process. Before authentication, the described outcome is primarily a service crash that can disrupt remote access. After successful user authentication, exploitation may result in remote code execution in the context of related processes.

The effect on confidentiality, integrity, and availability depends on the daemon's privileges and the resources accessible to its service account. Running xrdp as a non-privileged user can limit movement from process compromise to operating system administrator access, but it does not prevent compromise within that account's permissions. The evidence does not confirm persistence, lateral movement, or impact to other systems.

Business impact

  • Service disruption: Pre-authentication exploitation can crash the xrdp process and interrupt users' ability to establish or maintain remote desktop sessions.
  • Code execution risk: Post-authentication exploitation may allow remote code execution in the context of the xrdp process.
  • Data and system exposure: If code execution succeeds, an attacker may access, modify, or disrupt resources available to the service account.
  • Privilege-dependent scope: Running the daemon as a non-privileged user can limit the ability to escalate from process compromise to operating system administrator access. If the daemon runs with greater privileges, the potential consequences may be broader.
  • The record provides no evidence of a specific breach, victim, persistence, or lateral movement.

Remediation

  1. Upgrade to xrdp 0.10.6, the version the vendor confirms as patched for this issue.
  2. If an immediate upgrade is not possible, configure xrdp to run as a non-privileged user through runtime_user and runtime_group in xrdp.ini. This reduces the potential impact of remote code execution but does not remove the vulnerability.
  3. After changing the configuration, verify that the running daemon actually uses the restricted service account rather than relying only on the configuration file contents.
  4. Reduce exposure to untrusted networks while awaiting the upgrade if the deployment model permits. This limits reachability but is not a patch.
  5. Do not infer that other branches or releases are safe merely because 0.10.6 is patched. For operating-system packages, reconcile the package version with the distributor's corresponding security update.

Detection

  1. Inventory every host running xrdp, determine the installed version from the package manager or binary, and flag installations within the affected range.
  2. Identify xrdp services reachable from untrusted networks, especially systems that allow external clients to establish RDP sessions.
  3. Inspect xrdp.ini, focusing on runtime_user and runtime_group, and confirm that the daemon runs under a non-privileged service account.
  4. Review service logs, crash reports, and RDP connection telemetry for unexpected xrdp termination following malformed or failed RDP sessions. This is precautionary monitoring, not a vendor-confirmed indicator.
  5. Do not treat the absence of crash logs or other suspicious activity as proof that a system is safe. The available evidence provides no specific IOC or log signature.
Sources (13)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.