Information Disclosure in github.com/rclone/rclone (CVE-2026-88013)
Summary
Vulnerability in github.com/rclone/rclone (CVE-2026-88013). Risk of unauthorized operations or information disclosure. Exploitable via CheckRedirect. Mitigation: upgrade to 1.75.1 or later.
Original description
The description as published by the source.
rclone is a command-line program to sync files and directories to and from different cloud storage providers. From 1.49.0 until 1.75.1, the HTTP backend attaches headers configured through --http-headers or headers= to requests in backend/http/http.go, while its fshttp.NewClient client follows redirects without a backend-specific http.Client.CheckRedirect policy. A configured remote that redirects to another host can therefore cause custom secrets such as X-Api-Key to be resent to that untrusted destination, and a same-host HTTPS-to-HTTP redirect can expose Authorization or Cookie headers in cleartext. Listing, stat, download, mount, and serve operations can trigger the leak during normal use. This issue is fixed in version 1.75.1.
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-88013 has been found in github.com/rclone/rclone.
Attackers can target a specific entry point like CheckRedirect over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/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-88013" on the vendor's site.
CVE-2026-88013 (github.com/rclone/rclone) — CWE-200 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CheckRedirect / addHeaders / http / http.Client.CheckRedirect
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.
Information disclosure (CWE-200) exists in github.com/rclone/rclone. Attackers reach the vulnerable code path via CheckRedirect without authentication.
Check the vendor advisory for the affected versions of github.com/rclone/rclone. Attack surface: CheckRedirect / addHeaders / http / http.Client.CheckRedirect.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
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
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-88013 rclone
- Ubuntu UBUNTU-CVE-2026-88013 rclone
References
- advisory github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web nvd.nist.gov
- web github.com