Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-88014 medium CVSS 6.3

Path Traversal in github.com/rclone/rclone (CVE-2026-88014)

Summary

Path traversal in github.com/rclone/rclone (CVE-2026-88014). Data can be tampered with by attackers. Exploitable via file.Name. Mitigation: upgrade to 1.75.1 or later.

Original description

The description as published by the source.

Summary

backend/archive mounts a zip file as a browsable, syncable rclone Fs (e.g. rclone lsf :zip:downloaded.zip or rclone copy :zip:downloaded.zip dest:). Go's archive/zip package does not sanitize file.Name - it is taken verbatim from the untrusted zip's central directory. readZip() in backend/archive/zip/zip.go applies path.Clean to the entry name, but this alone cannot fully neutralize a name with more .. components than real segments preceding them (e.g. "../../etc/cron.d/evil" stays exactly as-is after cleaning). When the archive is mounted with an empty root (the common case), there was no check at all that the resulting name stayed inside the archive's own namespace, so it was stored verbatim and returned unchanged by Object.Remote().

fs/sync/fs/operations use srcObj.Remote() directly as the destination-relative path when copying between filesystems, so a maliciously crafted zip file can cause rclone copy/sync to attempt writes outside the intended destination directory on whatever backend it targets - this is the well-known "Zip Slip" vulnerability class (https://security.snyk.io/research/zip-slip-vulnerability) applied to rclone's own zip-mounting backend. It is distinct from cmd/archive/extract, which already validates via its own destPath() choke point and is not affected.

Details

Vulnerable code (before fix), backend/archive/zip/zip.go, (*Fs).readZip:

for _, file := range zr.File {
	remote := strings.Trim…

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-88014 has been found in github.com/rclone/rclone.
Attackers can target a specific entry point like file.Name over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.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-88014" on the vendor's site.

CVE-2026-88014 (github.com/rclone/rclone) — CWE-22 / CVSS v3 6.3
Attack vector: local / unauthenticated
Attack surface: file.Name / path.Clean / sync / strings.HasPrefix
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.

❓ What is the problem

Path traversal (CWE-22) exists in github.com/rclone/rclone. Attackers reach the vulnerable code path via file.Name without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/rclone/rclone. Attack surface: file.Name / path.Clean / sync / strings.HasPrefix.

🔥 Severity

Severity: Medium (CVSS 6.3/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.75.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/rclone/rclone to 1.75.1

    ステージング環境で 1.75.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/rclone/rclone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.75.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details