# CVE-2026-114044: FreeRDP before 3.32.1 Android Client Heap OOB Read via Graphics Pipeline


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114044, GHSA-262p-h989-vmpv, GHSA-mp7g-v56c-664p, UBUNTU-CVE-2026-114044

## What is CVE-2026-114044?

CVE-2026-114044 is a medium-severity vulnerability in FreeRDP, published on 21 Oct 2026. 

### Official description

FreeRDP before 3.32.1 contains a heap out-of-bounds read vulnerability in the Android client that allows malicious RDP servers to read beyond surface buffers by supplying unvalidated mappedWidth and mappedHeight values. Attackers can send a crafted RDPGFX_MAP_SURFACE_TO_WINDOW_PDU with oversized dimensions, causing android_UpdateWindowFromSurface to copy heap memory beyond the allocation, leading to crashes or memory disclosure.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Upgrade to a fixed version.

## Is CVE-2026-114044 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114044 is a medium-severity vulnerability in FreeRDP, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114044 in the wild and no public exploit code.

Affected product: FreeRDP. 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-114044/ (Markdown: https://insights.sbomify.com/CVE-2026-114044/index.md)
```

## Sources

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

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