This CVE reveals a path traversal vulnerability that exploits how rclone's character encoding configuration interacts with filesystem path resolution. The root cause is that certain encoding modes—Slash, None, Raw, and Windows backslash-preserving modes—do not transform or reject traversal sequences like '../' before filepath.Join processes them. The OS interprets these sequences as parent-directory navigation regardless of what the encoding layer was intended to handle.
If you're running rclone, check your configuration: any backend using these encoding modes (the default is generally safe, but custom configurations often specify them for international filename handling) creates a path where adversarial input can escape the intended root. The attack requires the attacker to control or influence path components in the sync operation—file names, directory names, or symbolic links. In typical rclone deployments, this means an attacker who can place files in a synced source location can write to arbitrary locations on the destination as the rclone process user.
The deployment context amplifies the severity significantly. Rclone rarely runs interactively; it's used in backup jobs, CI/CD pipelines, scheduled sync tasks, and cloud migrations—often as root or with elevated filesystem privileges. Arbitrary file write in this context means the ability to modify cron jobs, SSH authorized_keys, systemd units, or configuration files that subsequent processes will execute. This isn't just data exfiltration risk; it's a privilege escalation vector.
The fix landed in v1.75.0. The critical question for your environment: did the patch add validation at the encoding layer (rejecting traversal sequences in encoded filenames) or at the path resolution layer (making filepath.Join enforce root boundaries)? If it's only the former, legitimate international filenames using fullwidth characters or similar CJK conventions may break post-upgrade. If it's the latter, backward compatibility for international filenames was preserved while closing the traversal gap. Check the rclone release notes and test your specific filename set before deploying.
For immediate hardening: audit existing rclone configurations for explicit encoding mode settings, especially in automation pipelines where configurations may have been set and forgotten. Pinning a vulnerable version carries the vulnerability forward indefinitely—the vulnerable versions (v1.51.0 through v1.75.0) represent years of deployed automation that won't auto-upgrade. The EPSS score likely reflects theoretical risk from the pattern being well-documented in prior CVEs (URL encoding bypasses, Samba encoding issues), but the narrow exploitation requirement means this targets specific, high-value pipelines rather than opportunistic scanning.