CVE-2026-79782
rclone leaks AWS STS tokens over HTTP when S3 redirects change HTTPS->HTTP
Is CVE-2026-79782 being exploited?
Not confirmed. CVE-2026-79782 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-79782?
CVE-2026-79782 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-79782?
Yes. A fix has been recorded for CVE-2026-79782. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-79782 affect?
CVE-2026-79782 affects rclone < 1.74.4, Clients using rclone with S3 endpoints that redirect HTTPS->HTTP, Systems relying on AWS STS tokens in transit. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-79782?
Upgrade rclone to >=1.74.4 and rotate any exposed AWS STS tokens
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Intercepted HTTP redirect can expose AWS STS session tokens, enabling unauthorized AWS access, data exfiltration, and resource misuse.
Immediate action required
- affected< 1.74.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.