<Vulnerability name="CVE-2026-88046">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Moderate</ThreatSeverity>
    <PublicDate>2026-09-10T16:14:49</PublicDate>
    <Bugzilla id="2531548" url="https://bugzilla.redhat.com/show_bug.cgi?id=2531548" xml:lang="en:us">
github.com/rclone/rclone: rclone: Unauthorized data modification via path traversal in source object names
    </Bugzilla>
    <CVSS3 status="draft">
        <CVSS3BaseScore>5.3</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-22</CWE>
    <Details xml:lang="en:us" source="Mitre">
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.
    </Details>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in rclone, a command-line program for syncing files. This vulnerability allows an attacker to bypass configured directory restrictions by including parent-directory segments (e.g., '..') in source object names. When a specially crafted source object is uploaded or copied, it can enable unauthorized access or modification of data outside the intended storage location. This could lead to data being written to unintended buckets, shares, or filesystem paths accessible by the victim's credentials.
    </Details>
    <Mitigation xml:lang="en:us">
This flaw requires an untrusted, flat-keyspace source object store, populated by tooling other than rclone, that contains a raw .. key segment. Syncs or copies from such sources should avoid destination backends that construct paths with path.Join(root, remote): b2, swift, qingstor, oracleobjectstorage, internetarchive, smb, storj, sftp, webdav, ftp, filelu, shade, and sia. 

Restricting untrusted-source syncs to destinations outside this list, or auditing source object keys for .. segments beforehand, prevents the path traversal until rclone is upgraded to 1.75.1.
    </Mitigation>
    <PackageState cpe="cpe:/a:redhat:cryostat:4">
        <ProductName>Cryostat 4</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>cryostat/cryostat-storage-rhel9</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:acm:2">
        <ProductName>Red Hat Advanced Cluster Management for Kubernetes 2</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>rhacm2/volsync-rhel9</PackageName>
    </PackageState>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-88046
https://nvd.nist.gov/vuln/detail/CVE-2026-88046
https://github.com/rclone/rclone/commit/57842c5ee4e1407eda06a414a36510cce2db4252
https://github.com/rclone/rclone/releases/tag/v1.75.1
https://github.com/rclone/rclone/security/advisories/GHSA-38xv-hf3p-h7mq
    </References>
</Vulnerability>