CVE-2026-71309

rclone: Incomplete path validation allows backend root escape in serve restic

Published Aug 5, 2026 CVSS 4.0 · 8.6 High EPSS < 1% KEV · Not listed
Description
rclone is a command-line program to sync files and directories to and from different cloud storage providers. From 1.40.0 until 1.75.0, rclone serve restic does not correctly reject URL paths beginning with ../ in cmd/serve/restic/restic.go WithRemote, which accepts a leading parent path and passes it to GET, HEAD, POST, and DELETE handlers for configured backends including WebDAV, FTP, HTTP, Memory, and SFTP. An attacker who can access the REST endpoint may read, create, overwrite, or delete objects outside the path configured by the operator when the operator publishes a backend subdirectory and the backend credential can access parent or sibling objects. This issue is fixed in 1.75.0.

Analysis

AI-generated

Technical impact

rclone’s serve restic feature incorrectly accepts URL paths starting with '..', allowing the parent directory to be passed to backend handlers. This path traversal flaw lets an attacker read, create, overwrite, or delete objects outside the intended root directory when the REST endpoint is reachable and the backend credentials have access to those broader paths.

Affected Systems

Rclone, versions 1.40.0 through 1.74.9 (any release prior to 1.75.0), are affected. The vulnerability applies to all supported backends including WebDAV, FTP, HTTP, Memory, and SFTP.

Risk and Exploitability

With a CVSS score of 8.6, the flaw is considered high severity. No EPSS score is available, so the current likelihood of exploitation cannot be quantified, and the issue is not listed in CISA’s KEV catalog. Exploitation requires an attacker to reach the rclone REST interface; once exposed, a malicious user can issue arbitrary REST requests that result in path traversal and unauthorized file manipulation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade rclone to version 1.75.0 or later to apply the fix
  • Restrict network access to the rclone REST endpoint, allowing only trusted IPs or networks
  • Avoid publishing backend subdirectories or remove backend credentials that grant access to parent or sibling paths

Generated by OpenCVE AI on August 5, 2026 at 21:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-45pq-889g-fcgh rclone: Incomplete path validation allows backend root escape in serve restic
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

threat_severity

Important

Type Values Removed Values Added
First Time appeared Rclone
Rclone rclone
Vendors & Products Rclone
Rclone rclone
Type Values Removed Values Added
Description rclone is a command-line program to sync files and directories to and from different cloud storage providers. From 1.40.0 until 1.75.0, rclone serve restic does not correctly reject URL paths beginning with ../ in cmd/serve/restic/restic.go WithRemote, which accepts a leading parent path and passes it to GET, HEAD, POST, and DELETE handlers for configured backends including WebDAV, FTP, HTTP, Memory, and SFTP. An attacker who can access the REST endpoint may read, create, overwrite, or delete objects outside the path configured by the operator when the operator publishes a backend subdirectory and the backend credential can access parent or sibling objects. This issue is fixed in 1.75.0.
Title rclone: Incomplete path validation allows backend root escape in serve restic
Weaknesses CWE-22
References
Metrics cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 6, 2026, 1:45 PM
Reserved
Aug 5, 2026, 6:14 PM
Status
Awaiting Analysis
Published
Aug 5, 2026, 9:16 PM
Modified
Sep 9, 2026, 8:50 PM
Severity
Important
Public date
Aug 5, 2026, 8:13 PM