Path Traversal in github.com/rclone/rclone (CVE-2026-71309)
Summary
Path traversal in github.com/rclone/rclone (CVE-2026-71309). Risk of unauthorized operations or information disclosure. Exploitable via GET /../. Mitigation: upgrade to 1.75.0 or later.
Original description
The description as published by the source.
In rclone serve restic, the WithRemote middleware fails to properly sanitize URL paths beginning with "../" or containing ".". Because path.Clean preserves leading parent directory components in relative paths, requests with leading traversal sequences bypass validation. On affected backends (such as WebDAV, FTP, SFTP, HTTP, and memory), an attacker with access to the REST endpoint can read, create, overwrite, or delete objects outside the configured root directory.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-71309 has been found in github.com/rclone/rclone.
Attackers can target a specific entry point like GET /../ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/rclone/rclone to 1.75.0 or later.
If unsure, ask your IT team or search "github.com/rclone/rclone CVE-2026-71309" on the vendor's site.
CVE-2026-71309 (github.com/rclone/rclone) — CWE-22
Attack surface: GET /../ / DELETE /../locks/ / master / WithRemote
Patched: 1.75.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/rclone/rclone. Attackers reach the vulnerable code path via GET /../.
Check the vendor advisory for the affected versions of github.com/rclone/rclone. Attack surface: GET /../ / DELETE /../locks/ / master / WithRemote.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.75.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /../ requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/rclone/rclone' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/rclone/rclone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/rclone/rcloneを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /../' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /../への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/rclone/rclone to 1.75.0ステージング環境で 1.75.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /../ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-71309 rclone
- Ubuntu UBUNTU-CVE-2026-71309 rclone
References
- advisory github.com
- patch github.com
- web github.com
- web github.com
- web nvd.nist.gov