[CLSA-2026:1792659934] rsync: Fix of CVE-2026-53783
Type:
security
Severity:
Important
Release date:
2026-10-22 09:05:45 UTC
Description:
- CVE-2026-53783: fix a TOCTOU escape from rrsync's restricted directory by replacing the lexical-only Perl support/rrsync with upstream's Python one, which pins each validated path component through /proc/self/fd, fails closed on path anomalies, pins the receiver option directories a peer can pivot (--backup-dir, --partial-dir, alt-dest) and denies --copy-unsafe-links, device/special creation, a peer-selected --debug, remote --files-from in write-only mode and the no-overwrite auxiliary paths inside a restricted dir - NOTE: the replacement needs the new --drop-D option, backported from upstream b607369f; it makes a receiver refuse to create devices and special files without changing the file-list encoding the way --no-D does. support/ keeps shipping as non-executable documentation, so no installed program changes behaviour unless an operator has wired rrsync as an SSH forced command. rrsync is now Python rather than Perl - NOTE: one receiver-side spelling differs from upstream deliberately: a destination that already exists and is not a directory is pinned by its parent rather than by itself, because rsync replaces such a destination by unlinking its name, which the self-pin spelling cannot support -- without this, pushing a file onto an existing file through rrsync failed. Path components above the destination stay pinned either way
CVEs fixed:
Updated packages:
  • rsync-3.2.3-19.el9_2.tuxcare.els22.aarch64.rpm
    sha:5d0aa4e26aefdd8f5c9ad9d2872089ea3e2f9a369876f2e88d07f5a53ccace62
  • rsync-3.2.3-19.el9_2.tuxcare.els22.i686.rpm
    sha:a49234814dd9d70cadf7ba1ef51f7b94e9a3fc0f7b7405cbc9ad7bac288719ef
  • rsync-3.2.3-19.el9_2.tuxcare.els22.x86_64.rpm
    sha:9898667c4dba63724e3d0c29192a1da2321b4ec6f6fe4e6cac47ca090d812c6b
  • rsync-daemon-3.2.3-19.el9_2.tuxcare.els22.noarch.rpm
    sha:c8260b51e11233ed57229456cc27579865e05b4fcd0b879bade9d2a6c615513d
Notes:
This page is generated automatically and has not been checked for errors. For clarification or corrections please contact the CloudLinux Packaging Team.