dbcve.org
RcloneApplication

CVE-2026-59733

HIGH · 8.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.74.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a path traversal vulnerability in rclone's serve restic --private-repos functionality. The authorization check uses a cleaned path, but the backend object key is built from the raw uncleaned URL path, allowing authenticated users to inject '..' sequences (e.g., //..//config) to escape their directory and read, overwrite, or delete other users' private repositories on backends that perform path component cleaning.

MitigationUpgrade rclone to version 1.74.4 or later to obtain the patch that properly sanitizes the URL path before constructing backend object keys.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RcloneApplication
Affected:< 1.74.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed rclone version
    Run 'rclone version' to get the exact version number
    Affected if Version is lower than 1.74.4 (e.g., 1.74.3, 1.74.2, etc.)
  2. Determine if serve restic is in use
    Check running processes or systemd service files for 'rclone serve restic' command usage, or review any startup scripts that invoke this command
    Affected if rclone serve restic is running as a service or process
  3. Check for --private-repos flag
    Examine the command line arguments used with 'rclone serve restic' (check process list with 'ps aux' or service configuration files)
    Affected if The --private-repos flag is present in the command line
  4. Identify backend type in use
    Review rclone configuration (typically in ~/.config/rclone/rclone.conf) to determine which backend is being served by restic
    Affected if The backend listed in the rclone.conf is one that performs path component cleaning (e.g., S3, Azure Blob, Google Cloud Storage, or other object storage backends)
  5. Verify network exposure
    Check if the restic serve endpoint is exposed to untrusted networks by reviewing firewall rules, reverse proxy configuration, or binding address (e.g., 'rclone serve restic --addr' setting)
    Affected if The service is listening on a non-loopback address accessible to other authenticated users

User is affected if running rclone version below 1.74.4 with 'serve restic --private-repos' enabled and an object storage backend, especially in multi-user or exposed network environments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.74.4 or later
Fixed in 1.74.4
Interim mitigation

Upgrade rclone to version 1.74.4 or later to obtain the patch that properly sanitizes the URL path before constructing backend object keys.

Recommended fix High confidence

1.74.4

  1. Download rclone version 1.74.4 or later from the official rclone downloads page (https://rclone.org/downloads/) or GitHub releases page
  2. Verify the installation by running 'rclone version' and confirming the version number is 1.74.4 or higher
  3. Restart any running instances of 'rclone serve restic' to ensure the patched version is running

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rclone Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59733 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data