Rsync is widely deployed on servers and backup appliances; remote read/write outside chroot can lead to widespread data theft or tampering across organizations.
CVE-2026-53793
rsync path-confinement bypass allows remote read/write outside module root
Is CVE-2026-53793 being exploited?
Not confirmed. CVE-2026-53793 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-53793?
CVE-2026-53793 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53793?
Yes. A fix has been recorded for CVE-2026-53793. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53793 affect?
CVE-2026-53793 affects rsync < 3.5.0, rsync daemon modules containing '/./' in module root, Unix/Linux servers running rsync daemon, Backup/NAS devices using rsync modules. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53793?
Upgrade to rsync >= 3.5.0; disable/restrict modules using '/./'; audit exposed rsync services.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote clients can escape module chroot via /./ or crafted delta paths to read and write files outside the module, enabling data theft or file tampering.
Immediate action required
- affected<= 3.4.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.