xrdp VNC-Any Integer Overflow Out-of-Bounds Read (CVE-2026-41521)

Technical Analysis

The flaw stems from improper validation of image dimension fields in screen update messages handled by the vnc-any backend of xrdp. When a malicious VNC server supplies oversized or crafted width/height values, the buffer size calculation overflows an integer, producing a smaller-than-expected allocation. Subsequent image processing routines then use the original, unclamped dimensions to read from this undersized buffer, causing an out-of-bounds heap read that can leak adjacent memory contents or crash the xrdp process (DoS). Exploitation requires the target xrdp instance to connect outbound to, or proxy through, an attacker-controlled or compromised VNC server, making this most relevant in reverse-proxy or gateway deployment scenarios. Remote-access and jump-box infrastructure running xrdp as a bridge to backend VNC services are the primary attack surface. Where xrdp gateways are used to provide remote desktop access into environments hosting AI agent orchestration hosts, RAG pipelines, or LLM tool-use servers, a successful heap read could expose credentials, API keys, or session tokens used by those agent systems, warranting inclusion under agent-relevant risk.

Affected Systems

xrdp versions 0.10.6 and prior configured with vnc-any connection mode; Linux distributions and remote access gateways deploying xrdp as an RDP-to-VNC bridge.

Indicators of Compromise

• No known file hashes, IPs, or domains associated with this vulnerability at disclosure; indicators would be specific to malicious VNC server endpoints used in exploitation attempts (not published).

Remediation Steps

1. 1

   Upgrade xrdp

   Update xrdp to version 0.10.6.1 or later, which contains the fix for the integer overflow and out-of-bounds read.

2. 2

   Restrict VNC backend trust

   Only permit xrdp vnc-any connections to trusted, vetted VNC servers; avoid exposing this connection mode to untrusted or internet-facing VNC endpoints.

3. 3

   Network segmentation

   Place xrdp gateways behind network controls that limit outbound VNC connections to known internal hosts, reducing exposure to malicious VNC servers.

4. 4

   Monitor for crashes/anomalies

   Monitor xrdp process logs for unexpected crashes or restarts that could indicate exploitation attempts.

5. 5

   Rotate exposed credentials

   If xrdp gateways provide access into environments running AI agent infrastructure, rotate API keys and session tokens accessible from affected hosts as a precaution against potential memory disclosure.