# CVE-2026-109250: FreeRDP 3.0.0 before 3.32.0 Heap Buffer Overflow via PKCS#11 collect_keys()

> Local attackers with smartcard control can trigger heap buffer overflow in FreeRDP during logon, potentially enabling code execution or privilege escalation.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109250, GHSA-jhv5-m83m-hxhq, GHSA-q5vf-vw79-qr24, UBUNTU-CVE-2026-109250

## What is CVE-2026-109250?

CVE-2026-109250 is a high-severity memory corruption vulnerability in FreeRDP, published on 12 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

FreeRDP 3.0.0 before 3.32.0 contains a heap buffer overflow vulnerability in collect_keys() that allows local attackers to write past the fixed 64-entry keys array during PKCS#11 key enumeration. Attackers controlling smartcard tokens can present more than 64 public key objects across multiple slots to corrupt heap memory with attacker-chosen CKA_ID and CKA_LABEL data during smartcard logon.

Weakness: CWE-129 (Improper Validation of Array Index)

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


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

Upgrade to a fixed version.

## Is CVE-2026-109250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109250 is a high-severity memory corruption vulnerability in FreeRDP, published on 12 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109250 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-109250/ (Markdown: https://insights.sbomify.com/CVE-2026-109250/index.md)
```

## Sources

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

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