# CVE-2026-114045: FreeRDP before 3.32.1 Heap Buffer Overflow via rdpsnd_server_select_format


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114045, GHSA-3m9q-g533-rqjq, GHSA-mmcj-w3hp-5m84, UBUNTU-CVE-2026-114045

## What is CVE-2026-114045?

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

### Official description

FreeRDP before 3.32.1 contains a heap-based buffer overflow in the server-side rdpsnd channel because an integer wraparound in rdpsnd_server_select_format() DVI_ADPCM block-alignment arithmetic bypasses validation. A malicious RDP client can send two SNDC_FORMATS PDUs with an nBlockAlign too small for nChannels, causing an unbounded heap write during server audio playback, potentially enabling code execution.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-114045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114045 is a high-severity vulnerability in FreeRDP, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114045 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-114045/ (Markdown: https://insights.sbomify.com/CVE-2026-114045/index.md)
```

## Sources

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

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