Bug 2521042 - CVE-2026-53793 rsync: rsync < 3.5.0 Path Confinement Bypass via /./ Boundary Marker in Chroot Mode [fedora-all]
Summary: CVE-2026-53793 rsync: rsync < 3.5.0 Path Confinement Bypass via /./ Boundary ...
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": ["e4b418e9-d0f9-48e9-ad1c-2...
Depends On:
Blocks: CVE-2026-53793
TreeView+ depends on / blocked
 
Reported: 2026-08-21 16:19 UTC by Srikanth Balasubramanian
Modified: 2026-08-27 01:11 UTC (History)
3 users (show)

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


Attachments (Terms of Use)

Description Srikanth Balasubramanian 2026-08-21 16:19:48 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 before 3.5.0 contains a path confinement bypass vulnerability that allows remote clients to escape the intended inner-module root confinement by constructing paths that resolve outside the chroot boundary when the module root contains a /./ boundary marker. Attackers can exploit improper handling of the /./ notation or forge delta-basis transfers referencing xname paths that cross the /./ boundary to gain unauthorized read or write access to files outside the module's subtree.

Comment 1 Fedora Update System 2026-08-26 06:54:53 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:11:59 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.