{"affected":[{"package":{"ecosystem":"Bitnami","name":"rclone","purl":"pkg:bitnami/rclone"},"ranges":[{"events":[{"introduced":"1.72.0"},{"fixed":"1.75.1"}],"type":"SEMVER"}],"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N","type":"CVSS_V3"}]}],"aliases":["CVE-2026-88014"],"database_specific":{"cpes":["cpe:2.3:a:rclone:rclone:*:*:*:*:*:go:*:*"],"severity":"Medium"},"details":"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.","id":"BIT-rclone-2026-88014","modified":"2026-09-24T09:11:53.607Z","published":"2026-09-19T08:49:48.242Z","references":[{"type":"FIX","url":"https://github.com/rclone/rclone/commit/5dae3adbf571a6cd9ba501eb47397a7e871e1ae0"},{"type":"FIX","url":"https://github.com/rclone/rclone/commit/6507e13d5a83789f500af96d7188c302c9d74d98"},{"type":"ARTICLE","url":"https://github.com/rclone/rclone/releases/tag/v1.75.1"},{"type":"ADVISORY","url":"https://github.com/rclone/rclone/security/advisories/GHSA-66hp-wgxq-6f5q"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-88014"}],"schema_version":"1.6.2","summary":"rclone archive/zip: Zip Slip via unsanitized zip entry names lets a malicious archive escape its own namespace"}