rsync
home FAQ resources features examples mailing lists bug-tracking current issues and debugging download documentation search Rsync Security Advisories If you are running an rsync older than 3.5.2, you should upgrade. 3.5.2 fixes every issue listed on this page. If you cannot upgrade, the advisories below give the affected versions and the conditions each issue needs. Several are only reachable in a non-default configuration, and some of the older ones can be mitigated from rsyncd.conf without an upgrade.
Security fix in 3.5.2 4 November 2026 Rsync 3.5.2 bounds sender-side checksum work that remained after the CVE-2026-70453 mitigation. Versions through 3.5.1 are affected. CVE-2026-119741 (HIGH) — a malicious receiver can supply weak checksums which collide with consecutive rolling windows and make the sender calculate a full strong checksum at every byte offset. Repeating this across public daemon connections can exhaust host CPU.
Security fixes in 3.5.0 August 13th, 2026 Rsync 3.5.0 fixes 33 security issues found during a focused audit of rsync's path handling and daemon protocol, a companion daemon-protocol fuzzing pass, and reports from external researchers. All releases up to and including 3.4.4 are affected, except where an individual advisory gives a narrower range — many do, so check the advisory before deciding what needs patching. Upgrade to 3.5.0.
See the 3.5.0 NEWS for the full changelog, and the GitHub security advisories for the individual reports. Several of these are only reachable in a non-default configuration — a daemon with "use chroot = no", a writable module, an rrsync restricted account, "proxy protocol = true", or a configured name converter or exec hook. The advisories say which. CVE-2026-53783 (HIGH) — rrsync restricted-directory escape (validation-vs-exec race + unsafe option allowlist) CVE-2026-53784 (HIGH) — Daemon module-root chdir escape under "use chroot = no" CVE-2026-53785 (HIGH) — --relative implied-parent creation escapes the destination tree CVE-2026-53786 (MEDIUM) — Daemon --filter merge file bypasses the module filter list CVE-2026-53788 (MEDIUM) — Daemon name-converter accepts newline-bearing names into its line protocol CVE-2026-53789 (MEDIUM) — Malicious sender expands --delete scope by reclassifying an implied parent CVE-2026-53790 (HIGH) — Command / argument injection via unquoted peer- or host-controlled values CVE-2026-53791 (CRITICAL) — PROXY-protocol mode lets a direct client spoof the daemon's source address CVE-2026-53792 (MEDIUM) — Receiver-supplied zero checksum block length drives sender matching negative CVE-2026-53793 (HIGH) — Chroot "/./" inner-module escape via a parent-component symlink CVE-2026-53794 (MEDIUM) — Remote peer disables the per-allocation sanity cap via --max-alloc=0 CVE-2026-53795 (HIGH) — Receiver write escape via an absolute --temp-dir / --link-dest disabling rename/link confinement CVE-2026-53796 (MEDIUM) — Non-daemon receiver destination-chdir symlink race (TOCTOU) CVE-2026-53797 (MEDIUM) — Sender source-tree parent-component symlink race -> out-of-tree disclosure CVE-2026-53798 (MEDIUM) — Daemon name-converter empty response maps an unknown name to uid/gid 0 CVE-2026-53799 (MEDIUM) — Receiver ACL/xattr application follows a symlink-race -> arbitrary ACL set (local privilege escalation) CVE-2026-53800 (MEDIUM) — Sender --remove-source-files unlink follows a parent-component symlink race -> arbitrary file deletion outside the source tree CVE-2026-53801 (MEDIUM) — Sender/daemon directory-scan enumeration escapes the transfer root / module -> out-of-tree disclosure CVE-2026-53802 (HIGH) — Arbitrary file read / transfer-shaping via symlinked operator-supplied input files CVE-2026-53803 (HIGH) — Arbitrary file write / privilege escalation via symlinked operator-supplied output paths CVE-2026-70452 (HIGH) — `hosts deny` fails OPEN when a configured hostname cannot be resolved, admitting the host it was meant to block CVE-2026-70453 (HIGH) — Quadratic CPU exhaustion in hash_search() from a crafted equal-weak-checksum chain CVE-2026-70454 (MEDIUM) — rsync-ssl establishes an unauthenticated TLS connection (no CA verification; no stunnel hostname binding) CVE-2026-70455 (HIGH) — Peer-controlled Zstandard worker exhaustion on an rsync daemon CVE-2026-70456 (HIGH) — Remote out-of-bounds heap write in read_args() when the argument count lands exactly on maxargs CVE-2026-70457 (MEDIUM) — Attacker-chosen-offset write in parse_size_arg() error formatting CVE-2026-70458 (HIGH) — Out-of-bounds write from a FLAG_HLINKED file entry accepted without -H CVE-2026-70459 (MEDIUM) — Per-connection daemon child crash from a crafted first incremental file list with a non-directory transfer root CVE-2026-70460 (HIGH) — Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-module symlink CVE-2026-70461 (HIGH) — Peer-driven one-byte heap out-of-bounds write in add_implied_include() CVE-2026-70462 (MEDIUM) — Peer-supplied MSG_IO_TIMEOUT defeats the client's own I/O timeout (signed overflow, and a non-positive value) CVE-2026-70463 (HIGH) — "auth users" ignores documented comma-only parsing, silently skipping a deny/read-only rule CVE-2026-70464 (HIGH) — Unauthenticated pre-transfer handshake DoS locks out an rsync daemon module Security fixes in 3.4.3 May 20th, 2026 Rsync 3.4.3 fixes six security issues.
Versions 3.4.2 and earlier are affected. See the 3.4.3 NEWS . CVE-2026-29518 — TOCTOU symlink race allowing local privilege escalation in daemon mode without chroot. Only "use chroot = no" is exposed. CVE-2026-43618 — integer overflow in compressed-token decoding, allowing a malicious sender to disclose process memory to an authenticated daemon peer. CVE-2026-43620 — out-of-bounds read in the receiver, letting a malicious server crash any client pulling from it.
CVE-2026-43619 — symlink races on the remaining path-based system calls under "use chroot = no", generalising CVE-2026-29518. CVE-2026-43617 — hostname ACL bypass on a daemon with "daemon chroot" set where the chroot lacks the libc resolver files. CVE-2026-45232 — off-by-one stack out-of-bounds write parsing an HTTP CONNECT proxy response. Client-side, and only when RSYNC_PROXY is set. Security-related fixes in 3.4.2 April 28th, 2026 Several security-relevant defects were fixed in 3.4.2.
None were assigned a CVE: rsync's fork-per-connection design scopes each of them to the attacker's own connection, which is equivalent to the client closing the socket itself. They were fixed as a matter of hygiene and to reduce the chance of a future exploitable combination. A signed integer overflow in the PROXY protocol v2 header parser, an invalid access to the files array, and a negative token value accepted by the compressed-stream decoder.
See the 3.4.2 NEWS . Security fixes in 3.4.0 January 14th, 2025 Rsync 3.4.0 fixes six security issues, the most serious of which allows a malicious server to write outside the destination directory on a client that pulls from it. Versions 3.3.0 and earlier are affected. See the 3.4.0 NEWS . CVE-2024-12084 — heap buffer overflow in the daemon's checksum handling. CVE-2024-12085 — information leak from uninitialised stack memory when comparing file checksums.
CVE-2024-12086 — a malicious server could enumerate and read arbitrary files from the client. CVE-2024-12087 — a malicious server could write outside the destination directory using --inc-recursive. CVE-2024-12088 — --safe-links failed to verify symlink targets containing other symlinks, allowing a path-traversal write. CVE-2024-12747 — symlink race in the sender when handling regular files. Improved file-list validation in 3.2.5 August 14th, 2022 If you are running an rsync older than 3.2.5 and pulling files from an untrusted server, upgrade to 3.2.5 to get some added file-list validation rules that should prevent the sender from sn
The rest of this page is on the live site.