CVE-2026-59733 rclone vulnerability
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.
Quick answer
rclone should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-59733 affects rclone and is rated high. Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Fix this first on exposed systems, shared services, and user-facing workflows. The practical fix is to upgrade rclone to 1.74.4 or a later patched release, then verify the risky path is closed.
- Inventory every server, app, package, desktop, device, container, or workflow that uses rclone.
- Check the installed version and configuration against CVE-2026-59733 and the linked advisory.
- Apply the vendor fix: upgrade rclone to 1.74.4 or a later patched release.
- Limit rclone serve, archive extraction, symlink handling, and remote storage access to trusted users.
- Disable or isolate the affected feature if you cannot update right away.
- Review rclone logs for path traversal, archive extraction, symlink writes, and cross-user repository access.
- Rotate secrets, rebuild affected systems, or reset sessions if you suspect compromise.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm rclone is running the patched version or the approved mitigation is active.
- Confirm affected public, admin, API, desktop, storage, or device access is limited to trusted users.
- Repeat a safe test of the risky workflow and confirm the issue no longer appears.
- Review logs after the fix for crashes, bypass attempts, file access, or suspicious changes.
- Save version, config, log, and scan evidence for your remediation record.
Trusted references
FAQ
What is affected by CVE-2026-59733?
rclone should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.