# CVE-2026-114043: Vulnerability in FreeRDP


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114043, GHSA-f3vg-h45x-6wgf, GHSA-wfxj-44r2-v2c3, UBUNTU-CVE-2026-114043

## What is CVE-2026-114043?

CVE-2026-114043 is a high-severity vulnerability in FreeRDP, published on 21 Oct 2026. 

### Official description

FreeRDP before 3.32.1 contains a heap-based out-of-bounds read in WinPR's clipboard PNG-to-CF_DIB synthesis because winpr_read_png_from_buffer() allocates a bit-packed buffer for PNGs with bit depth below 8, while winpr_bitmap_write_buffer() copies rows assuming one byte per pixel. A malicious RDP server can send a crafted low-bit-depth PNG clipboard payload that, when pasted by the victim, discloses megabytes of heap memory.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-114043 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114043 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114043 is a high-severity vulnerability in FreeRDP, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114043 exists.

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

## Sources

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

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