dbcve.org
RcloneApplication

CVE-2026-59732

MEDIUM · 5.0 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.74.4 or later.
See remediation →
53/100
Remediation priority · Moderate
No privileges 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 archive extract can write extracted files outside the user-selected destination prefix when extracting a crafted archive containing parent path components such as ../, allowing creation or overwrite of sibling objects in the same bucket or path scope. 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

Rclone versions prior to 1.74.4 contain a path traversal vulnerability in the archive extraction feature. When extracting archives, the software fails to properly validate that extracted file paths remain within the user-specified destination directory, allowing crafted archives containing parent path components (../) to write files outside the intended destination to sibling objects in the same bucket or path scope.

MitigationUpgrade rclone to version 1.74.4 or later. Until upgraded, avoid extracting untrusted archives and implement additional access controls on destination paths.

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
Low

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

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. Check installed rclone version
    Run `rclone version` or `rclone --version` and note the version number shown
    Affected if The version displayed is less than 1.74.4 (for example, 1.74.3, 1.74.2, 1.73.0, etc.)
  2. Identify archive extraction operations
    Review rclone configuration files (typically in ~/.config/rclone/rclone.conf) and any scripts or automation that use rclone commands with archive extraction flags such as `--unzip`, `--untar`, `--unrar`, or the `serve archive` command
    Affected if Archive extraction features (unzip, untar, unrar) are actively configured or used in rclone operations
  3. Audit extraction destination paths
    Examine the destination path specified in any archive extraction commands (the target directory argument after the archive source in commands like `rclone copyto` with archive flags)
    Affected if The destination path accepts user-controlled input or is used with archives from untrusted sources
  4. Inspect archive sources
    Review the source of archives being extracted: check if they originate from untrusted users, external sources, or user-uploaded content
    Affected if Archives being extracted come from sources that are not trusted or verified (e.g., user uploads, external URLs, shared buckets)

You are affected if rclone version is below 1.74.4 AND you use rclone to extract archives, particularly from untrusted or user-controlled sources, into destination paths that may then be accessed by other operations or users.

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. Until upgraded, avoid extracting untrusted archives and implement additional access controls on destination paths.

Recommended fix High confidence

1.74.4

  1. Download Rclone version 1.74.4 from the official Rclone website (https://rclone.org/downloads/) or from the GitHub releases page
  2. Verify the downloaded file's checksum matches the published SHA256 hash for version 1.74.4
  3. Install or upgrade to Rclone 1.74.4 using your preferred installation method (direct binary, package manager, or source build)

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

Fix this in Rclone Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59732 — 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-59732 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