Destination-tree file deletion via sender-controlled path reclassification
Published Aug 13, 2026 · Updated Aug 13, 2026
Improper path handling in rsync 3.4.4 and earlier allows remote attackers controlling a sender to delete files outside the destination tree. The receiver trusts sender-supplied flags when classifying implied-parent and synthetic-root file-list entries, allowing delete_in_dir or recursive deletion to run above the requested leaf. Exploitation requires a victim-initiated pull with --delete or --force, and it can erase receiver-owned files throughout the destination root.
Summary
What happened
Improper path handling in rsync 3.4.4 and earlier allows remote attackers controlling a sender to delete files outside the destination tree. The receiver trusts sender-supplied flags when classifying implied-parent and synthetic-root file-list entries, allowing delete_in_dir or recursive deletion to run above the requested leaf. Exploitation requires a victim-initiated pull with --delete or --force, and it can erase receiver-owned files throughout the destination root.
The record
- CVE
- CVE-2026-53789
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Rsync Project
- Product
- rsync
- Classifications
- CWE-807, T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.4.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo