CVE-2026-88013 rclone: http backend forwards custom/auth headers to a different host on redirect
Attackers can steal sensitive authentication headers by triggering redirects in rclone's HTTP backend, exposing secrets to untrusted hosts or cleartext.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-88013?
CVE-2026-88013 is a low-severity vulnerability in rclone, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-88013?
4 open source packages ship an affected version, including github.com/rclone/rclone and rclone. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/rclone/rclone Go | From 1.49.0 | 1.75.1 |
github.com/rclone/rclone Go | From 1.49.0 | 1.75.1 |
github.com/rclone/rclone Go | From 1.49.0 | 1.75.1 |
rclone Bitnami | From 1.49.0 | 1.75.1 |
Products include Rclone Rclone.
How do I fix CVE-2026-88013?
Upgrade github.com/rclone/rclone to 1.75.1 or later.
Is CVE-2026-88013 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88013 exists.
Other vulnerabilities in rclone
- CVE-2026-88018 rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass
- CVE-2026-49980 Rclone: Unauthenticated command execution in `rclone rcd --rc-serve` via inline remote instantiation, bypassing CVE-2026-41179 fix
- CVE-2026-41179 RClone: Unauthenticated operations/fsinfo allows attacker-controlled backend instantiation and local command execution
- CVE-2026-41176 Rclone: Unauthenticated options/set allows runtime auth bypass, leading to sensitive operations and command execution
- CVE-2026-59733 rclone `serve restic --private-repos` authorization bypass: `..` in the URL path lets an authenticated user read, overwrite and delete other users' repositories
Sources
Also known as BIT-rclone-2026-88013, DEBIAN-CVE-2026-88013, GHSA-486v-q2wf-fp2r, GO-2026-6463, MINI-4qg4-c4qw-752g, MINI-84fg-99wm-8w5x and 7 more.