Security advisory Debian

rsync 3.5.0 for Debian 13 fixes 33 CVEs (DSA-6527-1), plus the May 2026 update DSA-6282-1

Debian 13 moved to rsync 3.5.0 to fix 33 CVEs; Debian 12 got the May fixes but the September batch is still open. What to check and change.

Published
Reading time
4 min read

Security advisory Vulnerability

Severity: Critical Status: Monitoring
Status
Fixed in Debian 13 (trixie). As of 31 Oct 2026 Debian 12 (bookworm) has not received the September fixes; the article lists mitigations.
Affected
  • rsync in Debian 13 (trixie) before 3.5.0+ds1-0+deb13u1
  • rsync in Debian 13 (trixie) before 3.4.1+ds1-5+deb13u3
  • rsync in Debian 12 (bookworm) before 3.2.7-1+deb12u5
Published
Updated

What you should do

  • On Debian 13, upgrade to 3.5.0+ds1-0+deb13u1 and test backup scripts that rely on symlinked destinations.
  • On Debian 12, make sure you have at least 3.2.7-1+deb12u5, apply the mitigations above, and watch the rsync tracker page for a DLA.
  • Restart the rsync daemon after updating, or disable it if nothing needs it.
  • Review rrsync backup accounts and firewall TCP port 873.
Timeline
  1. Debian published DSA-6282-1 for rsync.
  2. Debian published DSA-6527-1 for rsync.
  3. Skyline published this summary.

On 28 September 2026 Debian published DSA-6527-1, moving rsync in Debian 13 (trixie) to upstream 3.5.0. That release fixes 33 security issues from an audit of rsync's path handling and daemon protocol. Earlier, on 20 May 2026, DSA-6282-1 fixed a smaller set for both Debian 12 and 13. Debian 12 (bookworm) has not yet received the September fixes.

At a glance

ReleaseInstall at leastAdvisoryStatus of the 33 September CVEs
Debian 13 (trixie)3.5.0+ds1-0+deb13u1DSA-6527-1 (28 Sep 2026)Fixed
Debian 12 (bookworm)3.2.7-1+deb12u5DSA-6282-1 (20 May 2026)Listed as open in the Debian tracker on 31 Oct 2026

Severity: Critical by the rsync project's own label for CVE-2026-53791, which only applies to daemons with proxy protocol = true; most of the others are rated high or medium. None of the CVEs is in CISA's Known Exploited Vulnerabilities catalog (30 Oct 2026).

What the vulnerabilities are

Debian says the September issues could result in local privilege escalation, bypass of intended access restrictions, information disclosure, denial of service or the execution of arbitrary code, and points to the rsync 3.5.0 NEWS for details. The upstream notes group them as follows:

  • Symlink following by a privileged rsync. A local user who controls part of a path plants a symlink that rsync running as root then follows. CVE-2026-53803 (high) can redirect writes such as --log-file or batch files, for example appending to authorized_keys; CVE-2026-53802 (high) can read an arbitrary file through filter, files-from or password files.
  • Daemon access control. CVE-2026-53791 (critical) lets a client spoof its source address with a PROXY header when proxy protocol = true. CVE-2026-70452 makes hosts deny fail open when a listed hostname cannot be resolved. CVE-2026-53784 is a module-root escape with use chroot = no.
  • Injection and memory safety. CVE-2026-53790 covers command or argument injection through unquoted host or peer values in RSYNC_CONNECT_PROG, daemon exec hooks and rsync-ssl. Several heap out-of-bounds writes can crash or corrupt the daemon.
  • Availability. CVE-2026-70464 lets an unauthenticated peer hold daemon connections open past max connections.
  • rrsync. CVE-2026-53783 is an escape from the restricted directory of rrsync, the SSH wrapper often used for backup accounts.

The May update (DSA-6282-1) fixed, among others, CVE-2026-43618, an integer overflow that could leak process memory to an authenticated daemon peer, and symlink races in daemons with use chroot = no (CVE-2026-29518, CVE-2026-43619). The upstream notes say the default use chroot = yes is not exposed to those races.

Are you affected?

apt policy rsync
systemctl is-active rsync
grep -nE 'use chroot|proxy protocol|hosts (allow|deny)' /etc/rsyncd.conf

Every machine with rsync installed should be updated, but the daemon, root-run backup jobs and rrsync accounts are where most of these issues bite.

How to update

sudo apt update
sudo apt install --only-upgrade rsync

On Debian 13 this installs 3.5.0. Its NEWS lists behaviour changes worth testing in backup scripts: a symlinked destination directory is followed only if the link is owned by root or the running user (--insecure-links restores the old behaviour), and proxy protocol = true without proxy protocol hosts now rejects all connections.

Restart or reboot?

No reboot. Restart the daemon where it runs:

sudo systemctl restart rsync

Scheduled jobs use the new binary on their next run.

Debian 12 until a fix arrives

Bookworm is now handled by Debian LTS, and the tracker lists the September CVEs as open there. Until a DLA appears, reduce exposure: keep the daemon off the internet or disabled (sudo systemctl disable --now rsync), keep the default use chroot = yes, use IP addresses rather than hostnames in hosts allow and hosts deny, and avoid running rsync as root over directories that other users can write to.

Sources

SKYLINE Engineering

@skyline

The engineering team at SKYLINE Industrial Solutions. We publish field-tested guides drawn from real KSA and GCC deployments.

See author profile
SKYLINE engineering services

Need this implemented for you?

Reading is free — building it right takes a team. SKYLINE engineers ship Debian for Aramco vendors, banks, hospitals and government agencies across Saudi Arabia. Talk to us before you start.

Aramco Approved Contractor ISO 9001 · ISO 27001 SAMA CSF aligned NCA ECC ready 247+ KSA clients

Comments

0 total · 0 threads
Be the first to leave a comment.