rclone before v1.75.0 fails to sanitize IBM IAM bearer tokens and SSE-C encryption keys during S3 redirect callbacks, allowing credentials to be preserved across scheme or host changes. Attackers observing network traffic from a trusted endpoint can capture reusable IBM IAM tokens on same-host HTTPS-to-HTTP downgrades or SSE-C keys on cross-origin redirects to access protected S3 objects.
CVE-2026-79780
Score 5.3 from GitHub Security Advisory published 2026-08-25. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (1)
Auto-updated Aug 25, 2026S3 Redirect Sanitization Omits IBM IAM Bearer Tokens and SSE-C Keys · Advisory · rclone/rclone · GitHub
https://github.com/rclone/rclone/security/advisories/GHSA-8mxv-9xhp-86h4Vendor Advisories for CVE-2026-79780(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/rclone/rclone | — | 1.75.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-29 13:04 UTCGHSA enrichment
- 2026-08-28 14:10 UTCGHSA enrichment
- 2026-08-27 15:17 UTCEG score recompute
- 2026-08-27 15:17 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 16:24 UTCEG score recompute
- 2026-08-26 16:24 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 16:24 UTCEG score recompute
- 2026-08-25 15:30 UTCEG score recompute
- 2026-08-25 15:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-79780?
When was CVE-2026-79780 disclosed?
Is CVE-2026-79780 actively exploited?
What is the CVSS score of CVE-2026-79780?
How do I remediate CVE-2026-79780?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-79780
Is Your Infrastructure Affected by CVE-2026-79780?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.