Is CVE-2026-59733 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-59733 being exploited in the wild.

How severe is CVE-2026-59733?

High severity, with a CVSS score of 8.8, published 14 July 2026.

Which products and versions are affected?

github.com/rclone/rclone (Go) <= 1.74.3, SEMVER:introduced=0,fixed=1.74.4; Rclone < 1.74.4, <= 1.74.3.

Is there a fix for CVE-2026-59733?

Yes. github.com/rclone/rclone (Go): upgrade to 1.74.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-59733 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-59733?

Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-59733: Rclone path traversal in serve restic private-repos

Q: Is there a fix for CVE-2026-59733?

Yes. github.com/rclone/rclone (Go): upgrade to 1.74.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-59733 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-59733?

Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-59733 · Severity: high · CVSS 8.8 · Published 2026-07-14

A security flaw in rclone's restic server mode allows one user to access another user's private backup files. Rclone is a tool used to manage and sync files across different storage providers. In multi-tenant setups where multiple users share the same server, an authenticated user can bypass isolation controls to read, modify, or delete the backup data of other customers.

Technologies: github.com/rclone/rclone (Go), Rclone. Vendors: Go, Rclone.

Quick answers

Is CVE-2026-59733 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-59733 being exploited in the wild.
How severe is CVE-2026-59733?: High severity, with a CVSS score of 8.8, published 14 July 2026.
Which products and versions are affected?: github.com/rclone/rclone (Go) <= 1.74.3, SEMVER:introduced=0,fixed=1.74.4; Rclone < 1.74.4, <= 1.74.3.
Is there a fix for CVE-2026-59733?: Yes. github.com/rclone/rclone (Go): upgrade to 1.74.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-59733 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-59733?: Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/rclone/rclone (Go): upgrade to 1.74.4 or later
```
go get github.com/rclone/rclone@v1.74.4
```

Technical details

An authorization bypass exists in `cmd/serve/restic/restic.go` when the `--private-repos` flag is used. The vulnerability is caused by a path desynchronization between two middlewares: `checkPrivate` validates the user based on a routed path segment, while `WithRemote` extracts the backend object path from the raw, uncanonicalized URL. By using path traversal sequences (e.g., `/me/../victim/`), an authenticated attacker can satisfy the authorization check for their own namespace while the backend resolves the final path to a different user's repository. This affects backends that perform POSIX-style path cleaning, such as SFTP, FTP, and the internal memory backend. The issue is addressed in version 1.74.4.

Affected products

rclone rclone <= 1.74.3

Identifiers

CVE-2026-59733
GHSA-fqj9-69pf-6pjg
GO-2026-6195

Timeline

2026-07-08: disclosed
2026-08-05: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.