CVE-2026-88014 json
rclone archive/zip: Zip Slip via unsanitized zip entry names lets a malicious archive escape its own namespace
published 2026-09-10 59 d ago modified 2026-09-24 46 d ago also BIT-rclone-2026-88014 , EUVD-2026-75574 , GHSA-66hp-wgxq-6f5q , GO-2026-6464
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/rclone/rclone 1.75.1
- bitnami rclone 1.75.1
- rclone rclone 1.75.1
- govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260916T180043-160000.1.1
suse advisories SUSE-SU-2026:23855-1SUSE-SU-2026:23863-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260916T180043-160000.1.1
opensuse advisories openSUSE-SU-2026:21897-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-88014 updated cvss 5.9
github.com/rclone/rclone: rclone: Arbitrary file write via Zip Slip vulnerability
-
Red Hat Cryostat 4 cryostat/cryostat-storage-rhel9 Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/volsync-rhel9affected: workaround, no fix available “No viable mitigation exists for this flaw.”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 59 d ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/rclone/rclone/security/advisories/GHSA-66hp-wgxq-6f5q referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N |
| GitHub | 3.1 | 6.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N |
| OSV | 3.1 | 6.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/rclone/rclone | >=1.72.0, <1.75.1 |
1.75.1 |
| bitnami | rclone | >=1.72.0, <1.75.1 |
1.75.1 |
Affected products
- rclone rclone
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/rclone/rclone/commit/5dae3adbf571a6cd9ba501eb47397a7e871e1ae0
web, patch
-
github.com
/rclone/rclone/commit/6507e13d5a83789f500af96d7188c302c9d74d98
web, patch
-
github.com
/rclone/rclone/security/advisories/GHSA-66hp-wgxq-6f5q
exploit, web, vendor-advisory, advisory
-
github.com
/rclone/rclone/releases/tag/v1.75.1
web, release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-88014
advisory, web
-
github.com
/rclone/rclone
package
Sources
- CVE List CVE-2026-88014
- GitHub Advisory GHSA-66hp-wgxq-6f5q
- NVD CVE-2026-88014
- OSV BIT-rclone-2026-88014
- OSV GO-2026-6464
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.