# CVE-2026-109244: FreeRDP 2.0.0 before 3.32.0 Insecure Private Key Permissions in winpr-makecert

> Local attackers can read world-readable private keys generated by winpr-makecert, leading to credential theft on multi-user systems.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/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-109244, GHSA-2jfv-j3wx-5cg4, GHSA-jww6-v76j-hqqx, UBUNTU-CVE-2026-109244

## What is CVE-2026-109244?

CVE-2026-109244 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 2.0.0 before 3.32.0 contains an insecure permission vulnerability in winpr-makecert that creates unencrypted private keys without owner-only file modes. Local users on multi-user Unix hosts can read world-readable key files or open PFX files protected by the hard-coded default password to steal private keys.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-109244 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109244 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: There is no known exploitation of CVE-2026-109244 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-109244/ (Markdown: https://insights.sbomify.com/CVE-2026-109244/index.md)
```

## Sources

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

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