02
rsync 3.5.2 fixes a remotely triggerable CPU-exhaustion flaw
The rsync project released version 3.5.2 to address CVE-2026-119741, a flaw in checksum matching that can let a malicious receiver consume a sender’s CPU with repeated unsuccessful calculations. The report says versions through 3.5.1 are affected and that anyone can trigger the issue against a public daemon module without an account. The release also adds options to lower CPU and I/O scheduling priority for transfers.
What changed Version 3.5.2 closes the checksum-processing flaw that allowed a connecting client to consume server CPU with unsuccessful calculations.
Why it matters Public rsync operators face an availability risk through the service’s normal file-pulling function: attackers need no account, and a few connections can exhaust CPU capacity. The reported impact is resource exhaustion, not data compromise.
HelpNet Security ↗