# 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.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **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, MINI-ch7f-h269-59jr, MINI-f243-946w-hxm8, MINI-fwwf-jq63-fpmc, MINI-g4hq-4vhc-5pvg, MINI-gx6g-grmg-3p44, MINI-pmh7-f34j-jg93, UBUNTU-CVE-2026-88013

## 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.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-319 (Cleartext Transmission of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## 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 | Ecosystem | 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: 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](https://insights.sbomify.com/CVE-2026-88018/): rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass (critical 9.8)
- [CVE-2026-49980](https://insights.sbomify.com/CVE-2026-49980/): Rclone: Unauthenticated command execution in `rclone rcd --rc-serve` via inline remote instantiation, bypassing CVE-2026-41179 fix (critical 9.8)
- [CVE-2026-41179](https://insights.sbomify.com/CVE-2026-41179/): RClone: Unauthenticated operations/fsinfo allows attacker-controlled backend instantiation and local command execution (critical 9.2)
- [CVE-2026-41176](https://insights.sbomify.com/CVE-2026-41176/): Rclone: Unauthenticated options/set allows runtime auth bypass, leading to sensitive operations and command execution (critical 9.2)
- [CVE-2026-59733](https://insights.sbomify.com/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 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88013 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88013 exists.

Affected packages and fixed versions:
- github.com/rclone/rclone (Go): affected from 1.49.0; fixed in 1.75.1
- github.com/rclone/rclone (Go): affected from 1.49.0; fixed in 1.75.1
- github.com/rclone/rclone (Go): affected from 1.49.0; fixed in 1.75.1
- rclone (Bitnami): affected from 1.49.0; fixed in 1.75.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88013/ (Markdown: https://insights.sbomify.com/CVE-2026-88013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88013
- OSV: https://osv.dev/vulnerability/CVE-2026-88013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88013/
Summaries are generated and may contain mistakes; the official description above is the record.