rclone (serve restic --private-repos): MULTI-TENANT ISOLATION: --private-repos is meant to confine each authenticated

Impact

MULTI-TENANT ISOLATION: --private-repos is meant to confine each authenticated user to their own repository, but a .. in the URL path walks out of it. An authenticated tenant reads, overwrites and deletes other tenants' backup repositories - so the isolation flag you deployed specifically for multi-user backup does not hold.

Who can reach it

Any authenticated user of an rclone serve restic endpoint running with --private-repos.

What to do

Upgrade rclone and restart the serve restic instance. Audit repository contents and object timestamps for cross-user writes. Where possible back the separation with per-user storage credentials or separate buckets instead of trusting the path prefix.

References