rclone serve restic --private-repos authorization bypass: .. in the URL path lets an authenticated user read, overwrite and delete other users' repositories
CVE-2026-59733GHSA-fqj9-69pf-6pjg
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/rclone/rclone 1.74.4), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- <= 1.74.3
- Fixed in
- 1.74.4
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-fqj9-69pf-6pjg lists affected ranges: Go github.com/rclone/rclone >=0 <1.74.4 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6195 lists affected ranges: Go github.com/rclone/rclone >=0 <1.74.4 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-fqj9-69pf-6pjg lists affected ranges: Go github.com/rclone/rclone >=0 <=1.74.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-59733: 0.55% estimated exploitation activity in the next 30 days; percentile 46.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary rclone serve restic --private-repos exists to let one rclone instance host many users' restic backup repositories behind HTTP Basic auth while keeping each user confined to a path prefix of /<username/. The documentation states the flag "can be used to limit users to repositories starting with a path of /<username/", and the shipped test TestResticPrivateRepositories asserts that user test may reach /test/config but is 403-blocked from /otheruser/config. This isolation is the entire security purpose of the flag. The isolation is enforced by two independent chi middlewares that derive the username and the backend object path from two different sources, and the path source is never canonicalized. checkPrivate authorizes the request by comparing the routed {userID} path segment against the authenticated user, while WithRemote builds the backend object key from the raw, un-cleaned URL path. A request such as GET /<me/../<victim/config keeps the first path segment equal to the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-fqj9-69pf-6pjg
- Revision 2 · amended ·
Amended from osv record GO-2026-6195
- Revision 1 · created ·
Published from osv record GHSA-fqj9-69pf-6pjg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-59733 Advisory: rclone `serve restic --private-repos` authorization bypass: `..` in the URL path lets an authenticated user read, overwrite and delete other users' repositories IDs: CVE-2026-59733, GHSA-fqj9-69pf-6pjg Record: https://patchnext.com/advisories/cve-2026-59733 (revision 3, source checked 26 Oct 2026, 15:28 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/rclone/rclone 1.74.4. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/rclone/rclone: affected <= 1.74.3; fixed in 1.74.4 ## Suggested inspection (read-only) - Go github.com/rclone/rclone: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/rclone/rclone. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-fqj9-69pf-6pjg (OSV record GHSA-fqj9-69pf-6pjg lists affected ranges: Go github.com/rclone/rclone >=0 <1.74.4 (fixed)) - Verified: https://osv.dev/vulnerability/GO-2026-6195 (OSV record GO-2026-6195 lists affected ranges: Go github.com/rclone/rclone >=0 <1.74.4 (fixed)) - Verified: https://github.com/advisories/GHSA-fqj9-69pf-6pjg (GitHub-reviewed advisory GHSA-fqj9-69pf-6pjg lists affected ranges: Go github.com/rclone/rclone >=0 <=1.74.3) Commands are suggestions: review each one before running it.
Loading voting…