# CVE-2026-32623: xrdp: Heap buffer overflow in NeutrinoRDP channel reassembly

> A heap buffer overflow in the optional NeutrinoRDP module allows remote code execution or denial of service via malicious RDP data.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-32623, GHSA-phw3-qp59-x2v4, UBUNTU-CVE-2026-32623

## What is CVE-2026-32623?

CVE-2026-32623 is a high-severity memory corruption vulnerability in neutrinolabs xrdp, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

xrdp is an open source RDP server. Versions through 0.10.5 contain a heap-based buffer overflow vulnerability in the NeutrinoRDP module. When proxying RDP sessions from xrdp to another server, the module fails to properly validate the size of reassembled fragmented virtual channel data against its allocated memory buffer. A malicious downstream RDP server (or an attacker capable of performing a Man-in-the-Middle attack) could exploit this flaw to cause memory corruption, potentially leading to a Denial of Service (DoS) or Remote Code Execution (RCE). The NeutrinoRDP module is not built by default. This vulnerability only affects environments where the module has been explicitly compiled and enabled. Users can verify if the module is built by checking for --enable-neutrinordp in the output of the xrdp -v command. This issue has been fixed in version 0.10.6.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-32623?

It affects 1 product.


Products: Neutrinolabs Xrdp.

## How do I fix CVE-2026-32623?

Upgrade to a fixed version.

## Is CVE-2026-32623 being exploited?

There is no known exploitation of CVE-2026-32623 in the wild and no public exploit code.

## Other vulnerabilities in neutrinolabs xrdp

- [CVE-2026-41252](https://insights.sbomify.com/CVE-2026-41252/): xrdp: lib_palette_update Heap Buffer Overflow & RCE (critical 9.8)
- [CVE-2026-32105](https://insights.sbomify.com/CVE-2026-32105/): xrdp: RDP MAC signature (dataSignature) never verified on receive — integrity bypass in non-TLS mode (critical 9.3)
- [CVE-2026-44178](https://insights.sbomify.com/CVE-2026-44178/): xrdp: Channel Data Forwarding Fixed-Size Buffer Overflow (high 8.8)
- [CVE-2026-32107](https://insights.sbomify.com/CVE-2026-32107/): xrdp: Fail-open privilege drop in sesexec — child processes may execute as root if setuid fails (high 8.8)
- [CVE-2026-33689](https://insights.sbomify.com/CVE-2026-33689/): xrdp: Pre-authentication out-of-bounds reads in channel parsers (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32623 and fix it if it is affected.

What it is: CVE-2026-32623 is a high-severity memory corruption vulnerability in neutrinolabs xrdp, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32623 in the wild and no public exploit code.

Affected product: neutrinolabs xrdp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32623/ (Markdown: https://insights.sbomify.com/CVE-2026-32623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32623
- OSV: https://osv.dev/vulnerability/CVE-2026-32623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32623/
Summaries are generated and may contain mistakes; the official description above is the record.