Rsync versions before 3.4.3 contain an off-by-one out-of-bounds stack write vulnerability in the establish_proxy_connection() function in socket.c that allows network attackers to corrupt stack memory by sending a malformed HTTP proxy response. Attackers can exploit this by positioning themselves between the client and proxy or controlling the proxy server to send a response line of 1023 or more bytes without a newline terminator, causing a null byte to be written to an out-of-bounds stack address when the RSYNC_PROXY environment variable is set.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade rsync | May 25, 2026 | May 20, 2026 |
| Amazon_linux_2023 | — | Upgrade rsync-daemonUpgrade rsyncUpgrade rsync-debugsourceUpgrade rsync-debuginfo | Sep 30, 2026 | May 20, 2026 |
| Debian | — | Upgrade rsync | Jul 12, 2026 | Jul 12, 2026 |
| Freebsd | — | Upgrade rsync | Jun 15, 2026 | May 21, 2026 |
| Gentoo Linux | — | Upgrade net-misc/rsync. | Aug 16, 2026 | Aug 13, 2026 |
| Redhat_linux | — | No solution exists | Jul 17, 2026 | May 20, 2026 |
| Ubuntu | — | Upgrade rsyncUpgrade rsync (Ubuntu Pro) | May 25, 2026 | May 20, 2026 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Jun 22, 2026 | May 20, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub