CVE-2026-88014 rclone archive/zip: Zip Slip via unsanitized zip entry names lets a malicious archive escape its own namespace
Attackers can use malicious ZIP archives to write files outside the intended destination directory when syncing with rclone.
- 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
What is CVE-2026-88014?
CVE-2026-88014 is a medium-severity path traversal vulnerability in rclone, published on 10 Sep 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. From 1.72.0 until 1.75.1, the archive ZIP backend method (*Fs).readZip in backend/archive/zip/zip.go accepts archive/zip.File.Name values from an untrusted central directory and exposes cleaned entry names without ensuring that they remain inside the archive namespace. Entries such as ../../etc/cron.d/evil can survive path.Clean and become Object.Remote() values that fs/sync and fs/operations use as destination-relative paths, allowing rclone copy or sync to write outside the selected destination on backends that do not independently confine the path. The non-empty root check also used strings.HasPrefix without a path boundary, so root foo could incorrectly include sibling foobar entries. This issue is fixed in version 1.75.1.
Weakness: CWE-22
Which versions are affected by CVE-2026-88014?
4 open source packages ship an affected version, including github.com/rclone/rclone and rclone. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/rclone/rclone Go | From 1.72.0 | 1.75.1 |
github.com/rclone/rclone Go | From 1.72.0 | 1.75.1 |
github.com/rclone/rclone Go | From 1.72.0 | 1.75.1 |
rclone Bitnami | From 1.72.0 | 1.75.1 |
Products include Rclone Rclone.
How do I fix CVE-2026-88014?
Upgrade github.com/rclone/rclone to 1.75.1 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-88014 being exploited?
There is no known exploitation of CVE-2026-88014 in the wild and no public exploit code.
Other vulnerabilities in rclone
- CVE-2026-88018 rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass
- CVE-2026-49980 Rclone: Unauthenticated command execution in `rclone rcd --rc-serve` via inline remote instantiation, bypassing CVE-2026-41179 fix
- CVE-2026-41179 RClone: Unauthenticated operations/fsinfo allows attacker-controlled backend instantiation and local command execution
- CVE-2026-41176 Rclone: Unauthenticated options/set allows runtime auth bypass, leading to sensitive operations and command execution
- 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
Sources
Also known as BIT-rclone-2026-88014, DEBIAN-CVE-2026-88014, GHSA-66hp-wgxq-6f5q, GO-2026-6464, MINI-8fg2-9mcf-qp8h, MINI-cxj3-mfgp-2xqx and 3 more.