# 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.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N`)
- **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:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **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, MINI-p7ch-jvgm-3xp3, MINI-qm55-8wqr-463c, UBUNTU-CVE-2026-88014

## 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 (Improper Limitation of a Pathname to a Restricted Directory)

## 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 | Ecosystem | 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: Rclone Rclone.

## How do I fix CVE-2026-88014?

Upgrade github.com/rclone/rclone to 1.75.1 or later.

## 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](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-88014 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-88014 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/rclone/rclone (Go): affected from 1.72.0; fixed in 1.75.1
- github.com/rclone/rclone (Go): affected from 1.72.0; fixed in 1.75.1
- github.com/rclone/rclone (Go): affected from 1.72.0; fixed in 1.75.1
- rclone (Bitnami): affected from 1.72.0; fixed in 1.75.1

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-88014/ (Markdown: https://insights.sbomify.com/CVE-2026-88014/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88014
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88014
- OSV: https://osv.dev/vulnerability/CVE-2026-88014

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88014/
Summaries are generated and may contain mistakes; the official description above is the record.