Skip to content
VulniPulse
Advisory severityHigh7.5Red Hat Linux

High [CVE-2026-54572] Arbitrary file write via malicious symbolic link handling

This high-severity Red Hat Linux advisory covers CVE-2026-54572.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-54572 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Rclone is a command-line program to sync files and directories to and from different cloud storage providers.

Prior to 1.74.4, with -l/--links, rclone serializes symlinks as.rclonelink text objects and recreates them on a local destination without validating the target, allowing an attacker-controlled remote to plant an escaping symlink and cause a following object write to land outside the destination with attacker-chosen contents.

This issue is fixed in version 1.74.4. A remote attacker could exploit this by providing a malicious symlink, allowing subsequent file writes to occur outside the intended destination with content chosen by the attacker.

This could lead to unauthorized modification of files on the system. Rclone's -l/--links option serializes symbolic links encountered during a sync as `.rclonelink` text objects containing the link target, and later recreates those links on the destination.

Prior to 1.74.4, rclone did not validate that a stored link target stays within the intended destination tree before recreating it.

A remote storage backend under an attacker's control can therefore supply a crafted `.rclonelink` object whose target escapes the destination directory (e.g. via a `../` traversal or an absolute path), causing a subsequent write during the same or a later sync to be redirected outside the intended destination with attacker-chosen content.

Affected versions
  • < 1.74.4

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Fixed versions
  • 1.74.4

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade to rclone 1.74.4 or later, which validates symlink targets before recreating them and rejects links that would escape the destination directory. If an immediate upgrade is not possible, mitigate by avoiding the vulnerable code path: do not use the -l/--links command-line option when syncing to or from a remote that is not fully trusted, since this is what enables rclone to serialize and recreate symlinks in the first place.

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.