# CVE-2026-111880: FreeRDP 2.0.0 before 3.32.0 Heap Out-of-Bounds Write via NTLM MIC Offset

> Unauthenticated attackers can trigger a heap out-of-bounds write in FreeRDP via crafted NTLM messages, potentially leading to code execution or crashes.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 17 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-111880, GHSA-98x3-97xw-cfqr, GHSA-cmgx-558f-vh67, UBUNTU-CVE-2026-111880

## What is CVE-2026-111880?

CVE-2026-111880 is a high-severity memory corruption vulnerability in FreeRDP, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FreeRDP versions from 2.0.0 before 3.32.0 contain a heap out-of-bounds write in the server hash-callback NTLM path that fails to validate the MIC offset. Unauthenticated attackers can send a crafted AUTHENTICATE_MESSAGE with a backward session-key offset and MIC offset to write 16 zero bytes beyond the allocation.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2026-111880 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111880 is a high-severity memory corruption vulnerability in FreeRDP, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111880 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-111880/ (Markdown: https://insights.sbomify.com/CVE-2026-111880/index.md)
```

## Sources

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

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