BIT-rclone-2026-88046
See a problem?- Import Source
- https://github.com/bitnami/vulndb/tree/main/data/rclone/BIT-rclone-2026-88046.json
- JSON Data
- https://api.osv.dev/v1/vulns/BIT-rclone-2026-88046
- Aliases
- Published
- 2026-09-19T08:49:54Z
- Modified
- 2026-09-19T09:25:54Z
- Summary
- rclone: source object names can escape the configured root on upload
- Details
-
rclone is a command-line program to sync files and directories to and from different cloud storage providers. Prior to 1.75.1, rclone core does not reject parent-directory segments in source Object.Remote() values before fs/list, fs/walk, fs/sync, and fs/operations pass those values to destination backends. A flat-keyspace source object store populated with native non-rclone tooling can contain a raw .. key segment, and affected b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia destinations use path.Join(root, remote) before EncodeDot can neutralize the segment. A copy or upload can therefore escape the configured root into another bucket, share, or path reachable by the victim credential, with sftp and smb potentially reaching other filesystem or share locations under the same login authority. This issue is fixed in version 1.75.1.
- Database specific
{ "cpes": [ "cpe:2.3:a:rclone:rclone:*:*:*:*:*:go:*:*" ], "severity": "Medium" }- References
Affected packages
Bitnami / rclone
Package
- Name
- rclone
- Purl
- pkg:bitnami/rclone
Severity
- 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N CVSS Calculator