# rclone: S3 Redirect Sanitization Omits IBM IAM Bearer Tokens and SSE-C Keys Advisory record · `GHSA-8mxv-9xhp-86h4` - **Identifiers:** `GHSA-8mxv-9xhp-86h4` · `BIT-rclone-2026-79780` · `CVE-2026-79780` · `GO-2026-6188` - **State:** Confirmed - **Severity:** CVSS 6.0 Medium - **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:** 5 Aug 2026 - **Updated:** 25 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 5 Aug 2026, 20:27 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.75.0`; fixed in `1.75.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > GHSA-8mxv-9xhp-86h4: rclone versions before 1.75.0 are affected. When S3 requests carry IBM IAM bearer tokens or SSE-C encryption keys, a redirect that downgrades HTTPS to HTTP on the same host, or a cross-origin redirect, can forward those secrets to the redirect destination. An attacker positioned on the network path or at the redirect destination could capture a reusable bearer token or the keys. Upgrade to rclone 1.75.0 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 - 6.0 Medium, CVSS 4.0: `CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0015, the 3rd percentile, on 10 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-8mxv-9xhp-86h4) ## Sources - [GitHub Advisory Database: GHSA-8mxv-9xhp-86h4](https://github.com/advisories/GHSA-8mxv-9xhp-86h4) - [OSV: GHSA-8mxv-9xhp-86h4](https://osv.dev/vulnerability/GHSA-8mxv-9xhp-86h4) - - - - - 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: .