# CVE-2026-67295: FreeRDP before 3.29.0 Path Traversal via drive redirection

> A malicious RDP server can bypass shared-root boundaries in FreeRDP to read, write, delete, and enumerate files in sibling directories.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/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:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-67295, GHSA-8xqm-wp3f-rfp9, GHSA-mx9v-6x7q-rjc2, UBUNTU-CVE-2026-67295

## What is CVE-2026-67295?

CVE-2026-67295 is a medium-severity path traversal vulnerability in FreeRDP, published on 1 Aug 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 before 3.29.0 fails to properly validate server-supplied RDPDR paths in drive redirection, allowing attackers to access prefix-sibling paths outside the configured shared root. A malicious RDP server can read, write, delete, and enumerate files in sibling directories by sending non-rooted paths that bypass the shared-root boundary check.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

Upgrade to a fixed version.

## Is CVE-2026-67295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67295 is a medium-severity path traversal vulnerability in FreeRDP, published on 1 Aug 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-67295 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-67295/ (Markdown: https://insights.sbomify.com/CVE-2026-67295/index.md)
```

## Sources

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

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