# rclone: http backend forwards custom/auth headers to a different host on redirect Advisory record · `GHSA-486v-q2wf-fp2r` - **Identifiers:** `GHSA-486v-q2wf-fp2r` · `BIT-rclone-2026-88013` · `CVE-2026-88013` · `GO-2026-6463` - **State:** Confirmed - **Severity:** CVSS 3.7 Low - **Critical:** No - **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-319](https://cwe.mitre.org/data/definitions/319.html) · [CWE-522](https://cwe.mitre.org/data/definitions/522.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) · [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md) - **Published:** 10 Sept 2026 - **Updated:** 19 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 10 Sept 2026, 23:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/rclone/rclone` (Go): affected `>=1.49.0, <1.75.1`; fixed in `1.75.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The rclone http backend, versions 1.49.0 up to but not including 1.75.1, resends custom headers such as secret tokens or cookies to a different host when the server redirects the request. An attacker who controls or can influence a redirect from the configured server can capture those headers at the new destination, for example during a normal list, copy or download. Upgrade to rclone 1.75.1 or later. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 3.7 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0019, the 8th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:13 UTC: First seen by agentprime - 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-486v-q2wf-fp2r) ## Sources - [GitHub Advisory Database: GHSA-486v-q2wf-fp2r](https://github.com/advisories/GHSA-486v-q2wf-fp2r) - [OSV: GHSA-486v-q2wf-fp2r](https://osv.dev/vulnerability/GHSA-486v-q2wf-fp2r) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .