dbcve.org
Debian LinuxOperating system · Debian

CVE-2025-68670

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-27
Fix available
A fix is available. Upgrade to 0.10.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
xrdp is an open source RDP server. xrdp before v0.10.5 contains an unauthenticated stack-based buffer overflow vulnerability. The issue stems from improper bounds checking when processing user domain information during the connection sequence. If exploited, the vulnerability could allow remote attackers to execute arbitrary code on the target system. The vulnerability allows an attacker to overwrite the stack buffer and the return address, which could theoretically be used to redirect the execution flow. The impact of this vulnerability is lessened if a compiler flag has been used to build the xrdp executable with stack canary protection. If this is the case, a second vulnerability would need to be used to leak the stack canary value. Upgrade to version 0.10.5 to receive a patch. Additionally, do not rely on stack canary protection on production systems.

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 confidence

xrdp before v0.10.5 contains an unauthenticated stack-based buffer overflow during user domain information processing in the connection sequence. The vulnerability lacks proper bounds checking, allowing attackers to overwrite stack buffers and return addresses for remote code execution. Stack canary protection during compilation reduces but does not eliminate the risk.

MitigationUpgrade xrdp to version 0.10.5 immediately. Do not rely on compiler stack canary protection as a primary defense in production environments.

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
Debian LinuxOperating system
Affected:= 11.0
XrdpApplication
Affected:< 0.10.5

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify xrdp is installed
    Run 'dpkg -l | grep xrdp' on Debian/Ubuntu, or 'rpm -qa | grep xrdp' on RHEL/CentOS, or check for the binary at /usr/sbin/xrdp
    Affected if xrdp package or binary is found on the system
  2. Retrieve installed xrdp version
    Run 'xrdp -v' or 'xrdp --version', or use package manager: 'dpkg -l xrdp' (Debian) or 'rpm -qi xrdp' (RHEL)
    Affected if Version output shows a version number lower than 0.10.5
  3. Confirm xrdp service is running and exposed
    Run 'systemctl status xrdp' to check service status, then 'ss -tlnp | grep 3389' or 'netstat -tlnp | grep 3389' to verify the service is listening on port 3389
    Affected if xrdp service is active and bound to a network interface, making it reachable for exploitation
  4. Compare version against vulnerability range
    Interpret the version retrieved in step 2. The vulnerability affects all versions prior to 0.10.5, including 0.10.0 through 0.10.4
    Affected if Installed version is 0.10.4, 0.10.3, 0.10.2, 0.10.1, 0.10.0, or any 0.9.x version, or if version cannot be determined but xrdp is present on Debian 11

A system is affected if xrdp is installed and running with a version number lower than 0.10.5, exposing the vulnerable RDP connection processing code to network attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.10.5 or later
Fixed in 0.10.5
Vendor patch github.com →
Interim mitigation

Upgrade xrdp to version 0.10.5 immediately. Do not rely on compiler stack canary protection as a primary defense in production environments.

Recommended fix High confidence

xrdp v0.10.5

  1. Upgrade xrdp to version 0.10.5 or later. On Debian systems, run: apt update && apt install xrdp
  2. Verify the installed version matches or exceeds 0.10.5 using: xrdp --version
  3. Restart the xrdp service after upgrade: systemctl restart xrdp
  4. Ensure the system is not exposed to untrusted networks since this is an unauthenticated vulnerability
Caveat Standard upgrade; review release notes for any configuration changes in minor releases

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68670 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68670 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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