Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.0amended

rclone: S3 Redirect Sanitization Omits IBM IAM Bearer Tokens and SSE-C Keys

CVE-2026-79780GHSA-8mxv-9xhp-86h4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/rclone/rclone 1.75.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · score source
EPSS
  • CVE-2026-79780: 0.15% estimated exploitation activity in the next 30 days; percentile 3.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

1. Summary The S3 redirect callback strips X-Amz-Security-Token when a redirect changes scheme or host, but it does not strip IBM IAM bearer authorization or customer-provided encryption keys. Two independently validated paths remain: - a same-host HTTPS-to-HTTP redirect preserves Authorization: Bearer ... and exposes a reusable IBM IAM token to the plaintext network path; - a cross-origin redirect preserves SSE-C and copy-source SSE-C key headers. The High rating is driven by the reusable IBM IAM bearer token. The SSE-C cross-origin disclosure is a secondary confidentiality issue. The meaningful threat is a trusted endpoint, gateway, or accelerator that emits an unsafe redirect, followed by an adjacent/on-path observer; describing the originally configured endpoint itself as the attacker would be weak because that endpoint already receives the request secrets. 2. Affected Assets & Attack Surface - S3 redirect policy: backend/s3/s3.go:1345-1379 - IBM IAM signer:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-8mxv-9xhp-86h4

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6188

  4. Revision 1 · created ·

    Published from osv record GHSA-8mxv-9xhp-86h4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-79780

Advisory: rclone: S3 Redirect Sanitization Omits IBM IAM Bearer Tokens and SSE-C Keys
IDs: CVE-2026-79780, GHSA-8mxv-9xhp-86h4
Record: https://patchnext.com/advisories/cve-2026-79780 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/rclone/rclone 1.75.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rclone/rclone: affected <= 1.74.0; fixed in 1.75.0

## Suggested inspection (read-only)
- Go github.com/rclone/rclone: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/rclone/rclone.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8mxv-9xhp-86h4 (OSV record GHSA-8mxv-9xhp-86h4 lists affected ranges: Go github.com/rclone/rclone >=0 <1.75.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6188 (OSV record GO-2026-6188 lists affected ranges: Go github.com/rclone/rclone >=0 <1.75.0 (fixed))
- Verified: https://github.com/advisories/GHSA-8mxv-9xhp-86h4 (GitHub-reviewed advisory GHSA-8mxv-9xhp-86h4 lists affected ranges: Go github.com/rclone/rclone >=0 <=1.74.0)

Commands are suggestions: review each one before running it.

Loading voting…