Is CVE-2026-79780 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-79780 being exploited in the wild.

How severe is CVE-2026-79780?

Medium severity, with a CVSS score of 5.3, published 25 August 2026.

Which products and versions are affected?

github.com/rclone/rclone (Go) SEMVER:introduced=0,fixed=1.75.0; Rclone before v1.75.0.

Is there a fix for CVE-2026-79780?

Yes. github.com/rclone/rclone (Go): upgrade to 1.75.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-79780 attacked?

It is attacked over the network or from the adjacent network.

Am I affected by CVE-2026-79780?

Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-79780: rclone S3 redirect credential exposure in IBM IAM and SSE-C

CVE-2026-79780 · Severity: medium · CVSS 5.3 · Published 2026-08-25

rclone is a cloud storage synchronization tool widely used to manage data across cloud providers including Amazon S3. When rclone follows HTTP redirects during S3 operations, it fails to remove sensitive credentials (IBM IAM bearer tokens and encryption keys) before making requests to new endpoints, allowing an attacker observing network traffic to intercept and reuse these credentials to access protected data.

Technologies: github.com/rclone/rclone (Go), Rclone. Vendors: Go, Rclone.

Quick answers

Is CVE-2026-79780 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-79780 being exploited in the wild.
How severe is CVE-2026-79780?: Medium severity, with a CVSS score of 5.3, published 25 August 2026.
Which products and versions are affected?: github.com/rclone/rclone (Go) SEMVER:introduced=0,fixed=1.75.0; Rclone before v1.75.0.
Is there a fix for CVE-2026-79780?: Yes. github.com/rclone/rclone (Go): upgrade to 1.75.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-79780 attacked?: It is attacked over the network or from the adjacent network.
Am I affected by CVE-2026-79780?: Check whether you run github.com/rclone/rclone (Go) or Rclone at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/rclone/rclone (Go): upgrade to 1.75.0 or later
```
go get github.com/rclone/rclone@v1.75.0
```

Technical details

This vulnerability is a credential exposure issue (CWE-200, CWE-319) in rclone's S3 redirect handling callback (backend/s3/s3.go:1345-1379). The s3CheckRedirect function strips only the X-Amz-Security-Token header on cross-host redirects, but fails to sanitize IBM IAM Authorization: Bearer tokens or SSE-C/copy-source SSE-C encryption key headers. An attacker positioned on the network path can exploit this via: (1) same-host HTTPS-to-HTTP downgrades to capture plaintext IBM IAM bearer tokens, reusable within that token's IAM scope; or (2) cross-origin redirects to capture SSE-C encryption keys and access corresponding ciphertext. The attack requires network-adjacent positioning and a redirect from a trusted endpoint. Patch is available in rclone v1.75.0.

Affected products

rclone rclone before v1.75.0

Identifiers

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

Timeline

2026-07-31: disclosed: GitHub Security Advisory GHSA-8mxv-9xhp-86h4 published
2026-08-25: advisory: CVE-2026-79780 published
2026-07-31: patched: Fix released in v1.75.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.