CVE-2026-41521
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedxrdp is an open source RDP server. Versions 0.10.6 and prior contain an integer overflow vulnerability when processing screen update messages within the vnc-any connection mode. A malicious remote VNC server can send crafted image dimensions that cause an integer overflow during memory buffer size calculation, resulting in an undersized allocation. Subsequent processing of the incoming image data using the original oversized parameters leads to an out-of-bounds read. An unauthenticated remote attacker could exploit this flaw to disclose sensitive information from the heap memory or cause a denial of service (DoS) via a process crash. This issue has been fixed in version 0.10.6.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencexrdp versions 0.10.6 and prior contain an integer overflow in the vnc-any connection mode when processing screen update messages. A malicious VNC server sends crafted image dimensions that cause an integer overflow during memory buffer size calculation, resulting in an undersized allocation. Subsequent processing using the original oversized parameters leads to an out-of-bounds read, enabling heap memory disclosure or DoS via crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.10.6.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed xrdp versionRun 'xrdp --version' or 'rpm -q xrdp' (RHEL/CentOS) or 'dpkg -l xrdp' (Debian/Ubuntu) to determine the installed version numberAffected if Version is 0.10.6 or prior, or less than 0.10.6.1
-
Verify vnc-any connection mode is configuredInspect the xrdp configuration file (typically /etc/xrdp/xrdp.ini) and search for sections containing 'vnc-any' or 'vnc' connection type definitionsAffected if A vnc-any or vnc connection entry exists in the configuration
-
Confirm xrdp service is running and accepting connectionsCheck service status with 'systemctl status xrdp' or verify the process is active with 'ps aux | grep xrdp'Affected if The xrdp daemon is actively running and configured to accept connections
-
Identify if connections to untrusted VNC servers are possibleReview the vnc-any configuration parameters, specifically whether the allow list is empty or permits connections to arbitrary VNC servers, or check if users can specify custom VNC destinationsAffected if vnc-any mode permits connections to untrusted or arbitrary VNC servers without strict host validation
You are affected if xrdp version is below 0.10.6.1 AND the vnc-any connection mode is enabled and configured to allow connections to potentially untrusted VNC servers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.10.6.1
Upgrade xrdp to version 0.10.6.1 or later to patch the integer overflow vulnerability. Until upgrade, restrict or monitor vnc-any connections as an interim measure.
xrdp version 0.10.6.1
- Identify the current xrdp version installed on the system
- Upgrade xrdp to version 0.10.6.1 using the system's package manager (e.g., apt update && apt install xrdp=0.10.6.1, yum update xrdp, or compile from source)
- Restart the xrdp service to apply the changes (e.g., systemctl restart xrdp)
- Verify the installed version is 0.10.6.1 or later using 'xrdp --version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41521 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41521 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data