CVE-2025-68670: xrdp pre-authentication stack overflow (CVSS 9.1), fixed in 0.10.5 in January; canary-protected builds need a second flaw to exploit
Kaspersky details an xrdp pre-auth stack overflow fixed since January; exploitation of canary-protected builds needs a separate leak
Analysis
The xrdp project published advisory GHSA-rwvg-gp87-gh6f on 2026-01-27: xrdp before 0.10.5 contains an unauthenticated stack-based buffer overflow in the processing of user domain information during the connection sequence, rated critical with CVSS 3.1 9.1, which could let a remote attacker execute arbitrary code (xrdp, 2026-01-27). The impact is lessened where xrdp was built with stack canary protection, because a second vulnerability would then be needed to leak the canary value (xrdp, 2026-01-27). Kaspersky researchers, who reported the flaw on 2025-12-05, published their technical analysis on 2026-05-08: the vulnerable function copies a domain name of up to 512 bytes into a 256-byte stack buffer, the maintainers fixed it in 0.10.5 and backported the patch to 0.9.27 and 0.10.4.1, and Kaspersky's proof of concept stops at the canary check (Kaspersky Securelist, 2026-05-08). No source reports exploitation.
Updates1
The xrdp project disclosed and fixed this flaw on 2026-01-27 and scores it CVSS 9.1; builds with stack canary protection need a second vulnerability to leak the canary before the overflow can be exploited (xrdp, 2026-01-27). Kaspersky's article of 2026-05-08 is the reporting researchers' technical analysis, not the first disclosure (Kaspersky Securelist, 2026-05-08). The table of other CVEs that closed the earlier text belonged to unrelated findings and carried values their own sources contradict.
Sources2
Revision history
- Published 2026-05-09-migrated
- Correction 2026-10-11T1307Z-audit
The flaw was not newly disclosed on 2026-05-08: the xrdp project published its advisory and fix on 2026-01-27, and Kaspersky's article of 2026-05-08 is the researchers' later technical analysis. The entry omitted the project's CVSS 9.1 and the precondition that canary-protected builds need a second vulnerability, asserted a deployment breadth no source gives, and ended with a table of seven unrelated CVEs carrying wrong values; the table, the generic VPN action and the unsourced deployment claim are removed. The project advisory becomes the primary source, with a rating, an ATT&CK mapping and priority routine.
Changed: title headline summary event_date priority cves techniques sources classification actions body verification
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.