Path Traversal in github.com/rclone/rclone (CVE-2026-88046)
Summary
Path traversal in github.com/rclone/rclone (CVE-2026-88046). Data can be tampered with by attackers. Exploitable via Put. Mitigation: upgrade to 1.75.1 or later.
Original description
The description as published by the source.
Summary
Multiple backends, when given a specially crafted object to copy, can escape the backend confinement.
| Backend | Keep/Close | Per-backend severity |
|---|---|---|
| sftp | Medium | Real filesystem escape, fires under default encoding. |
| smb | Low-Medium | Escapes to a different SMB share the credential can reach. |
| ftp | Low | Real, leading-.. overshoot PoC is partly neutralized by encoding; escape bounded to at/below the login base. |
| webdav | Low | Server-side ACLs are the real boundary. |
| b2 | Low | Same-account sibling bucket crossing on a flat keyspace. |
| swift | Low | Same, container. |
| qingstor | Low | Same. |
| oracleobjectstorage | Low | Same. |
| internetarchive | Low | IA items are owner-writable only; confined to user's own items. |
| storj | Low | Can retarget a different bucket in the same access grant. |
| filelu | Low | Confined to the user's own account. |
| shade | Low | Confined to the user's own drive. |
| sia | Low | siad API password already grants full-daemon access. |
Root cause
rclone core does not sanitize .. in a source object's Remote() - verified: nothing in fs/march, fs/sync, fs/list, or fs/operations rejects .. segments before the name reaches the destination backend's Put/Update/Mkdir. Confinement is therefore each backend's responsibility, and these backends join root + remote without a check.
This divides into two classes:
- Bucket based backends - `bucket.Split(path.Join(f…
Source: NIST National Vulnerability Database 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-88046 has been found in github.com/rclone/rclone.
Attackers can target a specific entry point like Put over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: upgrade github.com/rclone/rclone to 1.75.1 or later.
If unsure, ask your IT team or search "github.com/rclone/rclone CVE-2026-88046" on the vendor's site.
CVE-2026-88046 (github.com/rclone/rclone) — CWE-22 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Put / Update / Mkdir / path.Join
Patched: 1.75.1 — 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 Put without authentication.
Check the vendor advisory for the affected versions of github.com/rclone/rclone. Attack surface: Put / Update / Mkdir / path.Join.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
Update to 1.75.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/rclone/rclone to 1.75.1ステージング環境で 1.75.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com