# CVE-2026-59732: rclone archive extract allows S3 destination prefix escape via crafted archive paths > Attackers can escape destination prefixes in rclone archive extraction to overwrite or read sibling objects in cloud storage buckets. - **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 Jul 2026 - **Updated:** 21 Jul 2026 - **Also known as:** BIT-rclone-2026-59732, DEBIAN-CVE-2026-59732, GHSA-4vr5-p2gc-h23p, GO-2026-6185, MINI-3r34-h54p-q8wp, MINI-49pv-rfpr-454p, MINI-5677-x4r6-64mw, MINI-8r82-gjhj-9gvm, MINI-hpxw-763m-42f5, MINI-v98p-mxgm-m479, UBUNTU-CVE-2026-59732 ## What is CVE-2026-59732? CVE-2026-59732 is a medium-severity path traversal vulnerability in rclone, published on 14 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### 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 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-59732? 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-59732? Upgrade github.com/rclone/rclone to 1.74.4 or later. ## Is CVE-2026-59732 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59732 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-59733](https://insights.sbomify.com/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 (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-59732 and fix it if it is affected. What it is: CVE-2026-59732 is a medium-severity path traversal vulnerability in rclone, published on 14 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59732 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-59732/ (Markdown: https://insights.sbomify.com/CVE-2026-59732/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59732 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59732 - OSV: https://osv.dev/vulnerability/CVE-2026-59732 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-59732/ Summaries are generated and may contain mistakes; the official description above is the record.