Skip to content
Fencer Vulns
medium 5.3

CVE-2026-42218 json

XRDP is vulnerable to a server timing attack, leading to user enumeration

published 2026-07-20 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-46024

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

xrdp is an open source RDP server. Versions 0.10.6 and prior contain a timing side-channel vulnerability in the login interface. Due to a discrepancy in response processing times, a remote attacker can infer the existence of a username on the system, leading to unauthorized information disclosure via username enumeration. This issue has been fixed in version 0.10.6.1.

Patch / fix

  • neutrinolabs xrdp 0.10.6.1
  • xrdp Debian 13 0.10.1-3.1+deb13u2
  • xrdp Debian 14 0.10.6.1-2

debian advisories DEBIAN-CVE-2026-42218

  • xrdp openSUSE Tumbleweed 0.10.6.1-1.1

opensuse advisories openSUSE-SU-2026:11543-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-42218 updated cvss 5.3

xrdp: timing side-channel allows username enumeration

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • neutrinolabs xrdp

Classification

Weakness
  • CWE-204 Observable Response Discrepancy

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.