# CVE-2026-54572: rclone: Unvalidated symlink target in local `--links` — arbitrary file write from an untrusted remote > An attacker can exploit unvalidated symlink targets in rclone's --links mode to write arbitrary files outside the destination directory. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 Jul 2026 - **Updated:** 15 Jul 2026 - **Also known as:** BIT-rclone-2026-54572, DEBIAN-CVE-2026-54572, GHSA-cf44-9pgv-m4xc, GO-2026-6191, MINI-4qqh-2gwc-2vq7, MINI-657r-6fww-m9hp, MINI-8cmq-cwr7-g472, MINI-mrr4-wmmg-7p3h, MINI-vp93-8qj2-5q4m, MINI-vvvc-63rq-8qw3, ROOT-APP-GOBINARY-CVE-2026-54572, UBUNTU-CVE-2026-54572 ## What is CVE-2026-54572? CVE-2026-54572 is a high-severity path traversal vulnerability in rclone, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, 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, with -l/--links, rclone serializes symlinks as .rclonelink text objects and recreates them on a local destination without validating the target, allowing an attacker-controlled remote to plant an escaping symlink and cause a following object write to land outside the destination with attacker-chosen contents. This issue is fixed in version 1.74.4. Weakness: CWE-59 (Improper Link Resolution Before File Access) ## Which versions are affected by CVE-2026-54572? 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-54572? Upgrade github.com/rclone/rclone to 1.74.4 or later. ## Is CVE-2026-54572 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54572 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-54572 and fix it if it is affected. What it is: CVE-2026-54572 is a high-severity path traversal vulnerability in rclone, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, 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-54572 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-54572/ (Markdown: https://insights.sbomify.com/CVE-2026-54572/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54572 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54572 - OSV: https://osv.dev/vulnerability/CVE-2026-54572 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-54572/ Summaries are generated and may contain mistakes; the official description above is the record.