CVE-2026-44978: xrdp: Unchecked FIPS padding length in standard RDP Security causes heap out-of-bounds read in HMAC verification

Published Jul 20, 2026
·
Updated

xrdp is an open source RDP server. Versions 0.10.6 and prior contain a heap out-of-bounds read vulnerability within the FIPS-specific receive paths. This vulnerability does not affect the default configuration of xrdp. The vulnerability is only exploitable when the security layer is set to securitylayer=negotiate or securitylayer=rdp, and the crypto level is changed to cryptlevel=fips in xrdp.ini. In this specific non-default mode, the server fails to validate the FIPS padding length field, leading to a pointer underflow and a subsequent negative length calculation. An unauthenticated remote attacker can exploit this by sending a crafted FIPS-protected PDU, causing a heap out-of-bounds read that results in a process crash and denial of service (DoS). However, since xrdp forks a new process for each connection by default, an out-of-bounds read causing a process crash is unlikely to bring down the entire xrdp service. This issue has been fixed in version 0.10.6.1.

Affected Software

2 affected components
xrdp xrdp<=0.10.6
Neutrinolabs Xrdp<0.10.6.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade xrdp to a version that resolves this vulnerability.

    Fixed in 0.10.6.1
  2. Configuration

    To avoid the vulnerable code paths, do not run xrdp with security_layer=negotiate or security_layer=rdp when using FIPS (crypt_level=fips). Use a security_layer other than 'negotiate' or 'rdp' in xrdp.ini (exact safe value not specified in the provided text).

    xrdp.ini security_layer = (ensure NOT negotiate/rdp)
  3. Configuration

    If you must avoid the vulnerable FIPS receive paths, do not set crypt_level=fips in xrdp.ini while using the affected security_layer values (security_layer=negotiate or security_layer=rdp).

    xrdp.ini crypt_level = (ensure NOT fips)
  4. Compensating control

    Because xrdp forks a new process per connection by default, DoS impact is limited; nevertheless, monitor for repeated process crashes/DoS conditions and ensure the service remains supervised/HA so overall availability is maintained.

Event History

Jul 20, 2026
CVE Published
via MITRE·04:56 PM
Data Sourced
via MITRE·04:56 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-44978?

CVE-2026-44978 has a medium severity rating of 5.3.

2

What is the impact of CVE-2026-44978 on xrdp?

CVE-2026-44978 can cause a heap out-of-bounds read during HMAC verification in xrdp if specific security configurations are used.

3

How do I fix CVE-2026-44978?

To remediate CVE-2026-44978, upgrade xrdp to version 0.10.6.1 or later.

4

Which versions of xrdp are affected by CVE-2026-44978?

xrdp versions 0.10.6 and prior are affected by CVE-2026-44978.

5

Is the default configuration of xrdp safe from CVE-2026-44978?

No, the vulnerability does not affect the default configuration of xrdp.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203