# CVE-2025-68118: Potential Heap Out-of-Bounds Read in freerdp_certificate_data_hash_ via Unsafe _snprintf Usage

> An attacker can trigger a heap out-of-bounds read in FreeRDP via crafted input, potentially causing a client crash or exposing memory contents.

- **Severity:** Medium 6.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** GHSA-h78c-5cjx-jw6x, MINI-fgj3-5xqq-mwvj

## What is CVE-2025-68118?

CVE-2025-68118 is a medium-severity memory corruption vulnerability in Freerdp Freerdp, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.20.0, a vulnerability exists in FreeRDP’s certificate handling code on Windows platforms. The function `freerdp_certificate_data_hash_ uses` the Microsoft-specific `_snprintf` function to format certificate cache filenames without guaranteeing NUL termination when truncation occurs. According to Microsoft documentation, `_snprintf` does not append a terminating NUL byte if the formatted output exceeds the destination buffer size. If an attacker controls the hostname value (for example via server redirection or a crafted .rdp file), the resulting filename buffer may not be NUL-terminated. Subsequent string operations performed on this buffer may read beyond the allocated memory region, resulting in a heap-based out-of-bounds read. In default configurations, the connection is typically terminated before sensitive data can be meaningfully exposed, but unintended memory read or a client crash may still occur under certain conditions. Version 3.20.0 has a patch for the issue.

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

## Which versions are affected by CVE-2025-68118?

It affects 1 product.


Products: Freerdp Freerdp.

## How do I fix CVE-2025-68118?

Upgrade to a fixed version.

## Is CVE-2025-68118 being exploited?

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

## Other vulnerabilities in Freerdp Freerdp

- [CVE-2021-37594](https://insights.sbomify.com/CVE-2021-37594/): Other in n/a (critical 9.8)
- [CVE-2021-37595](https://insights.sbomify.com/CVE-2021-37595/): Other in n/a (critical 9.8)
- [CVE-2026-67305](https://insights.sbomify.com/CVE-2026-67305/): FreeRDP Windows Client before 3.29.0 Heap Buffer Overflow via Cliprdr (critical 9.4)
- [CVE-2026-66402](https://insights.sbomify.com/CVE-2026-66402/): FreeRDP before 3.29.0 TLS Certificate Identity Validation Bypass (critical 9.3)
- [CVE-2026-67289](https://insights.sbomify.com/CVE-2026-67289/): FreeRDP before 3.29.0 HTTP Proxy Request Injection via Redirection (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68118 and fix it if it is affected.

What it is: CVE-2025-68118 is a medium-severity memory corruption vulnerability in Freerdp Freerdp, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68118 in the wild and no public exploit code.

Affected product: Freerdp 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-2025-68118/ (Markdown: https://insights.sbomify.com/CVE-2025-68118/index.md)
```

## Sources

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

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