# CVE-2026-71313: rclone: Local Encoding Path Traversal

> An attacker can exploit specific filename encodings to write or read files outside the intended directory when syncing data with rclone.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:L`)
- **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:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** BIT-rclone-2026-71313, DEBIAN-CVE-2026-71313, GHSA-7p4m-qxvv-g567, GO-2026-6186, MINI-2mhw-mr7x-v843, MINI-44fv-45xh-hv9h, MINI-5qv6-5v9h-w9wc, MINI-7ff8-5vhm-xxrj, MINI-c8r7-qpf5-85x7, MINI-jmc5-pr6v-qv7f, MINI-m67j-hx3w-wmqq, MINI-mpc2-3qxc-wq34, UBUNTU-CVE-2026-71313

## What is CVE-2026-71313?

CVE-2026-71313 is a medium-severity path traversal vulnerability in rclone, published on 5 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

rclone is a command-line program to sync files and directories to and from different cloud storage providers. From v1.51.0 until v1.75.0, the local backend in backend/local/local.go relies on the configurable filename encoder to prevent remote filename data from becoming operating-system path syntax, so a local destination using Slash, None, Raw, or on Windows an encoding that preserves backslash can decode a standard-encoded fullwidth dot-dot component or native backslash form into an actual parent-directory component before filepath.Join resolves it outside the configured local root, allowing an attacker-controlled source object to create or overwrite files outside the selected destination directory as the rclone process. This issue is fixed in v1.75.0.

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

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

4 open source packages ship an affected version, including github.com/rclone/rclone and rclone.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rclone/rclone` | Go | From 1.51.0 | 1.75.0 |
| `github.com/rclone/rclone` | Go | From 1.51.0 | 1.75.0 |
| `github.com/rclone/rclone` | Go | From 1.51.0 | 1.75.0 |
| `rclone` | Bitnami | From 1.51.0 | 1.75.0 |

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

Upgrade github.com/rclone/rclone to 1.75.0 or later.

## Is CVE-2026-71313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71313 is a medium-severity path traversal vulnerability in rclone, published on 5 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71313 exists.

Affected packages and fixed versions:
- github.com/rclone/rclone (Go): affected from 1.51.0; fixed in 1.75.0
- github.com/rclone/rclone (Go): affected from 1.51.0; fixed in 1.75.0
- github.com/rclone/rclone (Go): affected from 1.51.0; fixed in 1.75.0
- rclone (Bitnami): affected from 1.51.0; fixed in 1.75.0

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-71313/ (Markdown: https://insights.sbomify.com/CVE-2026-71313/index.md)
```

## Sources

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

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