Bug 2521726 - CVE-2026-70460 rsync: rsync 2.3.3 < 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink [fedora-all]
Summary: CVE-2026-70460 rsync: rsync 2.3.3 < 3.5.0 Path Traversal via --partial-dir/--...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rsync
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Michal Ruprich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["be16f6ce-21c0-42b7-9433-8...
Depends On:
Blocks: CVE-2026-70460
TreeView+ depends on / blocked
 
Reported: 2026-08-24 05:52 UTC by Srikanth Balasubramanian
Modified: 2026-08-27 01:12 UTC (History)
3 users (show)

Fixed In Version: rsync-3.5.0-1.fc43
Clone Of:
Environment:
Last Closed: 2026-08-27 01:12:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Srikanth Balasubramanian 2026-08-24 05:52:41 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

rsync 2.3.3 before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to escape the module root by exploiting symlinks within the module file tree when using --partial-dir or --backup-dir options. Attackers with write access to place a symlink under the module root, or who can exploit a pre-existing trusted symlink, can direct file writes to locations outside the intended module root, achieving arbitrary file write relative to the module root parent.

Comment 1 Fedora Update System 2026-08-26 06:54:56 UTC
FEDORA-2026-d6763b4c84 (rsync-3.5.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-d6763b4c84

Comment 2 Fedora Update System 2026-08-27 01:12:04 UTC
FEDORA-2026-d6763b4c84 (rsync-3.5.0-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.