# CVE-2026-114047: FreeRDP 2.0.0 before 3.32.0 Proxy Improper TLS Certificate Validation


- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114047, GHSA-2jg7-r42f-mvw7, GHSA-pjxv-5j98-cqx4, UBUNTU-CVE-2026-114047

## What is CVE-2026-114047?

CVE-2026-114047 is a high-severity vulnerability in FreeRDP, published on 21 Oct 2026. 

### Official description

FreeRDP from 2.0.0 before 3.32.0 contains an improper certificate validation vulnerability in its proxy that accepts untrusted target TLS certificates when no verification module is configured. Network-positioned attackers can intercept the proxy's outbound connection and present a self-signed, wrong-hostname certificate to impersonate the RDP target and receive proxied session data.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

Upgrade to a fixed version.

## Is CVE-2026-114047 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114047 is a high-severity vulnerability in FreeRDP, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114047 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-114047/ (Markdown: https://insights.sbomify.com/CVE-2026-114047/index.md)
```

## Sources

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

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