# CVE-2026-109677: FreeRDP 2.0.0-beta1 before 3.28.0 Out-of-Bounds Read via LocateCardsByATRA Handler

> Malicious RDP servers can trigger an out-of-bounds read in FreeRDP to leak heap memory, aiding ASLR bypass and remote code execution.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109677, GHSA-8m97-wwx3-r8vj, GHSA-fwx5-6r67-r722, UBUNTU-CVE-2026-109677

## What is CVE-2026-109677?

CVE-2026-109677 is a high-severity vulnerability in FreeRDP, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

FreeRDP from 2.0.0-beta1 before 3.28.0 contains an out-of-bounds read vulnerability in smartcard_LocateCardsByATRA_Call because the ATR pattern cbAtr byte count is not capped. Malicious RDP servers can send crafted ATR mask arrays to use query timing as an oracle, leaking heap memory bit-by-bit to defeat ASLR and aid RCE exploits.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-109677 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109677 is a high-severity vulnerability in FreeRDP, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-109677 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-109677/ (Markdown: https://insights.sbomify.com/CVE-2026-109677/index.md)
```

## Sources

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

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