rsync 3.4.2 < 3.5.0 DoS via --zt Zstandard Compression Thread Exhaustion
CVE-2026-70455 is fixed in 3 products on 1 platform, first by RHSA-2026:67463, released August 13, 2026. It is not reported as exploited. Patch Radar priority: High.
rsync 3.4.2 before 3.5.0 contains a denial of service vulnerability that allows a remote sender to exhaust system resources by specifying the --zt short alias for --compress-threads, which bypasses the refuse options directive's string matching on long option names. Attackers can specify --zt=N with a large value to spawn an unbounded number of Zstandard worker threads on the receiver, exhausting available thread and memory resources.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| rsync · Debian 13.5 (trixie) | 3.5.0+ds1-0+deb13u1 | DEBIAN-CVE-2026-70455 | Aug 27, 2026 |
| rsync · Debian 14 | 3.5.0+ds1-1 | DEBIAN-CVE-2026-70455 | Aug 27, 2026 |
| rsync · RHEL 10 | 3.5.0-3.el10_2 | RHSA-2026:67463 | Aug 13, 2026 |
| rsync · almalinux 10 | 3.5.0-3.el10_2 | ALSA-2026:67463 | Sep 14, 2026 |
| rsync · ol 10 | 0:3.5.0-3.el10_2 | ELSA-2026-67463-0 | Sep 16, 2026 |
| rsync · opensuse-leap 16.0 | 3.4.1-160000.6.1 | OPENSUSE-SU-2026:21650-1 | Aug 26, 2026 |
| rsync · rocky 10 | 0:3.5.0-3.el10_2 | RLSA-2026:67463 | Sep 15, 2026 |
| rsync · sles 15.6 | 3.2.7-150600.3.24.1 | SUSE-SU-2026:3657-1 | Aug 20, 2026 |
| rsync · sles 15.7 | 3.2.7-150600.3.24.1 | SUSE-SU-2026:3657-1 | Aug 20, 2026 |
| rsync · sles 16.0 | 3.4.1-160000.6.1 | SUSE-SU-2026:23323-1 | Aug 26, 2026 |
| rsync-daemon · almalinux 10 | 3.5.0-3.el10_2 | ALSA-2026:67463 | Sep 14, 2026 |
| rsync-daemon · ol 10 | 0:3.5.0-3.el10_2 | ELSA-2026-67463-0 | Sep 16, 2026 |
| rsync-rrsync · almalinux 10 | 3.5.0-3.el10_2 | ALSA-2026:67463 | Sep 14, 2026 |
| rsync-rrsync · ol 10 | 0:3.5.0-3.el10_2 | ELSA-2026-67463-0 | Sep 16, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.