# CVE-2026-109243: FreeRDP 3.0.0 before 3.32.0 Insecure Permissions on Soft-Smartcard Private Key File

> Local attackers can read world-readable private key files during soft-smartcard logon, exposing sensitive cryptographic material on multi-user systems.

- **Severity:** Medium 4.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-109243, GHSA-p86r-cw4x-6prq, GHSA-q9p9-j22r-577p, UBUNTU-CVE-2026-109243

## What is CVE-2026-109243?

CVE-2026-109243 is a medium-severity 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 from 3.0.0 before 3.32.0 contains an incorrect permission assignment vulnerability that allows local users to read private keys written by crypto_write_pem without owner-only permissions. Attackers on multi-user Unix hosts can enumerate the shared temporary directory during soft-smartcard logon to read the world-readable PKINIT private-key copy.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

Upgrade to a fixed version.

## Is CVE-2026-109243 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109243 is a medium-severity 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-109243 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-109243/ (Markdown: https://insights.sbomify.com/CVE-2026-109243/index.md)
```

## Sources

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

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