# CVE-2026-59733: rclone `serve restic --private-repos` authorization bypass: `..` in the URL path lets an authenticated user read, overwrite and delete other users' repositories

> Authenticated users can bypass private repository restrictions via path traversal to read, modify, or delete other users' data in rclone serve restic.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** BIT-rclone-2026-59733, DEBIAN-CVE-2026-59733, GHSA-fqj9-69pf-6pjg, GO-2026-6195, MINI-2q65-vhgr-3g79, MINI-cpg4-7prg-hm8j, MINI-hg6f-76p6-5p4j, MINI-jhg7-59cq-qv43, MINI-rgfv-vph2-x7hw, MINI-wc2j-xxmc-mp8x, ROOT-APP-GOBINARY-CVE-2026-59733, UBUNTU-CVE-2026-59733

## What is CVE-2026-59733?

CVE-2026-59733 is a high-severity path traversal vulnerability in rclone, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.74.4, rclone serve restic --private-repos enforces authorization using the routed user path segment while building the backend object key from the raw uncleaned URL path, allowing an authenticated user to include .. in a request such as //..//config and read, overwrite, or delete another user's private repository on backends that clean path components. This issue is fixed in version 1.74.4.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rclone/rclone` | Go | All versions | 1.74.4 |
| `github.com/rclone/rclone` | Go | All versions | 1.74.4 |
| `github.com/rclone/rclone` | Go | All versions | 1.74.4 |
| `rclone` | Bitnami | All versions | 1.74.4 |

Products: Rclone Rclone.

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

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

## Is CVE-2026-59733 being exploited?

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

## Other vulnerabilities in rclone

- [CVE-2026-88018](https://insights.sbomify.com/CVE-2026-88018/): rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass (critical 9.8)
- [CVE-2026-49980](https://insights.sbomify.com/CVE-2026-49980/): Rclone: Unauthenticated command execution in `rclone rcd --rc-serve` via inline remote instantiation, bypassing CVE-2026-41179 fix (critical 9.8)
- [CVE-2026-41179](https://insights.sbomify.com/CVE-2026-41179/): RClone: Unauthenticated operations/fsinfo allows attacker-controlled backend instantiation and local command execution (critical 9.2)
- [CVE-2026-41176](https://insights.sbomify.com/CVE-2026-41176/): Rclone: Unauthenticated options/set allows runtime auth bypass, leading to sensitive operations and command execution (critical 9.2)
- [CVE-2026-116191](https://insights.sbomify.com/CVE-2026-116191/): Rclone before 1.75.2 Path Traversal via serve webdav MKCOL (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59733 is a high-severity path traversal vulnerability in rclone, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59733 exists.

Affected packages and fixed versions:
- github.com/rclone/rclone (Go): affected all versions; fixed in 1.74.4
- github.com/rclone/rclone (Go): affected all versions; fixed in 1.74.4
- github.com/rclone/rclone (Go): affected all versions; fixed in 1.74.4
- rclone (Bitnami): affected all versions; fixed in 1.74.4

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

## Sources

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

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