CVE-2026-79779 rclone CVE debrief

Who should care

Defenders responsible for rclone deployments, particularly those using WebDAV operations, should assess exposure and prioritize upgrading to v1.75.0 or later. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal

Why it matters

Defenders should care about CVE-2026-79779 because it allows credential exposure via HTTP redirects in rclone versions before v1.75.0, potentially leading to unauthorized WebDAV operations. Verification of rclone versions and upgrades to v1.75.0 or later are necessary to prevent exploitation.

• Credential exposure via HTTP redirects
• Potential unauthorized WebDAV operations
• Need for rclone version verification and upgrades

Technical summary

rclone versions before v1.75.0 fail to reject transport downgrades in redirect handling, allowing Basic authorization and Cookie headers to be replayed over plaintext HTTP after same-host HTTPS-to-HTTP redirects. This vulnerability affects rclone deployments using WebDAV operations, particularly those with Basic authorization and Cookie headers. The vulnerability is caused by rclone's failure to properly handle redirects, which could lead to credential exposure and unauthorized WebDAV operations. Defenders should prioritize verifying rclone versions and upgrading to v1.75.0 or later to prevent exploitation.

Defensive priority

Defenders should prioritize verifying rclone versions and upgrading to v1.75.0 or later to prevent credential exposure.

Recommended defensive actions

• Verify rclone versions in use and upgrade to v1.75.0 or later
• Implement proper authentication and authorization for WebDAV operations
• Monitor for suspicious WebDAV activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but vendor statements and additional sources are limited. The vulnerability was disclosed on 2026-08-25T16:17:29.807Z. The CVE record was published on the same date and has not been modified since then. The NVD entry provides additional information on the vulnerability, including its CVSS score and severity. However, there is limited information available from the vendor or other sources regarding the vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.