{"id":"CVE-2026-70458","aliases":["ALPINE-CVE-2026-70458","ALSA-2026:67462","ALSA-2026:67463","ALSA-2026:74095","AZL-95759","BELL-CVE-2026-70458","CLSA-2026-1788335736","CLSA-2026-1789662743","CLSA-2026-1789730480","CLSA-2026-1789735848","CLSA-2026-1789737420","CLSA-2026-1789737518","CLSA-2026-1789749013","CLSA-2026-1789783256","CLSA-2026-1790173668","CLSA-2026-1790267010","CLSA-2026-1791331076","CLSA-2026-1791331932","DEBIAN-CVE-2026-70458","EUVD-2026-58046","GHSA-gg3m-4m9m-268h","MGASA-2026-0487","OESA-2026-3949","OESA-2026-3950","OESA-2026-4072","RHSA-2026:67462","RHSA-2026:67463","RHSA-2026:74095","RLSA-2026:67462","RLSA-2026:67463","RLSA-2026:74095","ROOT-OS-DEBIAN-11-CVE-2026-70458","SUSE-SU-2026:23253-1","SUSE-SU-2026:23254-1","SUSE-SU-2026:23289-1","SUSE-SU-2026:23323-1","SUSE-SU-2026:3634-1","SUSE-SU-2026:3657-1","UBUNTU-CVE-2026-70458","openSUSE-SU-2026:11869-1","openSUSE-SU-2026:21650-1"],"status":"published","title":"rsync 3.0.0 \u003c 3.5.0 Out-of-Bounds Write via FLAG_HLINKED Handling","description":"rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.","severity":{"version":"4.0","score":8.8,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00443,"percentile":0.3875,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-787"],"published":"2026-08-13T14:44:06Z","modified":"2026-11-09T05:00:10Z","fixes":[{"ecosystem":"Alpine:v3.21","package":"rsync","fixed_in":["3.5.0-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"rsync","fixed_in":["3.5.0-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"rsync","fixed_in":["3.5.0-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"rsync","fixed_in":["3.5.0-r0"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"rsync","fixed_in":["3.5.0-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"rsync","fixed_in":["3.5.0-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"rsync","fixed_in":["3.5.0-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"rsync","fixed_in":["3.5.0-r0"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"rsync","fixed_in":["3.5.0+ds1-0+deb12u1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"rsync","fixed_in":["3.5.0+ds1-0+deb13u1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"rsync","fixed_in":["3.5.0+ds1-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rsync","fixed_in":["3.2.3-4+deb11u4.aikido.1","3.2.3-4+deb11u4.aikido.2","3.2.3-4+deb11u4.aikido.3"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-rsync","fixed_in":["3.2.3-4+deb11u4.aikido.1","3.2.3-4+deb11u4.aikido.2","3.2.3-4+deb11u4.aikido.3"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.21","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.5.0-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.5.0-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.5.0-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.5.0-r0"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-1.el9_8"}]}],"bundled":20},{"source":"osv","ecosystem":"AlmaLinux:9","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-1.el9_8"}]}],"bundled":20},{"source":"osv","ecosystem":"AlmaLinux:9","package":"rsync-rrsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-1.el9_8"}]}],"bundled":20},{"source":"osv","ecosystem":"AlmaLinux:10","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.0-3.el10_2"}]}],"bundled":21},{"source":"osv","ecosystem":"AlmaLinux:10","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.0-3.el10_2"}]}],"bundled":21},{"source":"osv","ecosystem":"AlmaLinux:10","package":"rsync-rrsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.0-3.el10_2"}]}],"bundled":21},{"source":"osv","ecosystem":"AlmaLinux:8","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.3-28.el8_10"}]}],"bundled":17},{"source":"osv","ecosystem":"AlmaLinux:8","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.3-28.el8_10"}]}],"bundled":17},{"source":"osv","ecosystem":"Azure Linux:3","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.0-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.7-r0"},{"fixed":"3.5.0-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.4.1-r0"},{"fixed":"3.5.0-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.5-r0"},{"fixed":"3.5.0-r0"}]}]},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.3-6+tuxcare.els5"}]}],"bundled":15},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1-3ubuntu1.3+tuxcare.els17"}]}],"bundled":6},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.2-12.0.1.el7_9.tuxcare.els15"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.3-8ubuntu0.9+tuxcare.els11"}]}],"bundled":6},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.2-12.0.1.el7_9.tuxcare.els15"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-19.el9_2.tuxcare.els16"}]}],"bundled":8},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-19.el9_2.tuxcare.els16"}]}],"bundled":8},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.2-12.0.1.el7_9.tuxcare.els15"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.5-3.el9_6.tuxcare.els18"}]}],"bundled":7},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.5-3.el9_6.tuxcare.els18"}]}],"bundled":7},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rsync-rrsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.5-3.el9_6.tuxcare.els18"}]}],"bundled":7},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.3-12.el8.tuxcare.els15"}]}],"bundled":6},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.3-12.el8.tuxcare.els15"}]}],"bundled":6},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.3-19.el8.1.tuxcare.els11"}]}],"bundled":7},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.3-19.el8.1.tuxcare.els11"}]}],"bundled":7},{"source":"osv","ecosystem":"TuxCare:OracleLinux:6","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.6-12.el6.tuxcare.els11"}]}],"bundled":6},{"source":"osv","ecosystem":"TuxCare:CentOS:6","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.6-12.el6.tuxcare.els11"}]}],"bundled":6},{"source":"osv","ecosystem":"Debian:12","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.0+ds1-0+deb12u1"}]}],"versions":["3.2.7-1","3.2.7-1+deb12u1","3.2.7-1+deb12u2","3.2.7-1+deb12u3","3.2.7-1+deb12u4","3.2.7-1+deb12u5","3.2.7-1+deb12u6","3.3.0+ds1-1","3.3.0+ds1-2","3.3.0+ds1-3","3.3.0+ds1-4","3.3.0-1","3.4.1+ds1-1","3.4.1+ds1-2","3.4.1+ds1-3","3.4.1+ds1-4","3.4.1+ds1-4~exp1","3.4.1+ds1-4~exp2","3.4.1+ds1-5","3.4.1+ds1-5~exp1","3.4.1+ds1-6","3.4.1+ds1-7","3.4.1+ds1-8~exp1","3.4.2+ds1-1","3.4.2+ds1-2","3.4.3+ds1-1","3.4.3+ds1-2","3.4.4+ds1-1"]},{"source":"osv","ecosystem":"Debian:13","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.0+ds1-0+deb13u1"}]}],"versions":["3.4.1+ds1-5","3.4.1+ds1-5+deb13u1","3.4.1+ds1-5+deb13u2","3.4.1+ds1-5+deb13u3","3.4.1+ds1-5+deb13u4","3.4.1+ds1-6","3.4.1+ds1-7","3.4.1+ds1-8~exp1","3.4.2+ds1-1","3.4.2+ds1-2","3.4.3+ds1-1","3.4.3+ds1-2","3.4.4+ds1-1"]},{"source":"osv","ecosystem":"Debian:14","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.0+ds1-1"}]}],"versions":["3.4.1+ds1-5","3.4.1+ds1-6","3.4.1+ds1-7","3.4.1+ds1-8~exp1","3.4.2+ds1-1","3.4.2+ds1-2","3.4.3+ds1-1","3.4.3+ds1-2","3.4.4+ds1-1"]},{"source":"osv","ecosystem":"Mageia:10","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.1-1.mga10"}]}],"bundled":33},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-12.oe2403sp1"}]}],"bundled":33},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-12.oe2403sp3"}]}],"bundled":33},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP4","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-12.oe2403sp4"}]}],"bundled":33},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.2.7-1.el9_8"}]}],"bundled":20},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rsync-rrsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.2.7-1.el9_8"}]}],"bundled":20},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.2.7-1.el9_8"}]}],"bundled":20},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"rsync-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.2.7-1.el9_8"}]}],"bundled":20},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"rsync-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.2.7-1.el9_8"}]}],"bundled":20},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.2","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.5.0-3.el10_2"}]}],"bundled":21},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.2","package":"rsync-rrsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.5.0-3.el10_2"}]}],"bundled":21},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.2","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.5.0-3.el10_2"}]}],"bundled":21},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.2","package":"rsync-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.5.0-3.el10_2"}]}],"bundled":21},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.2","package":"rsync-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.5.0-3.el10_2"}]}],"bundled":21},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.1.3-28.el8_10"}]}],"bundled":17},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"rsync-daemon","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.1.3-28.el8_10"}]}],"bundled":17},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"rsync-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.1.3-28.el8_10"}]}],"bundled":17},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"rsync-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.1.3-28.el8_10"}]}],"bundled":17},{"source":"osv","ecosystem":"Rocky Linux:9","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.2.7-1.el9_8"}]}],"bundled":20},{"source":"osv","ecosystem":"Rocky Linux:10","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.5.0-3.el10_2"}]}],"bundled":21},{"source":"osv","ecosystem":"Rocky Linux:8","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.1.3-28.el8_10"}]}],"bundled":17},{"source":"osv","ecosystem":"Root:Debian:11","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-4+deb11u4.aikido.1"},{"fixed":"3.2.3-4+deb11u4.aikido.2"},{"fixed":"3.2.3-4+deb11u4.aikido.3"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-4+deb11u4.aikido.1"},{"fixed":"3.2.3-4+deb11u4.aikido.2"},{"fixed":"3.2.3-4+deb11u4.aikido.3"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-8.1"}]}],"bundled":37},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.0-slfo.1.1_7.1"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.1-160000.6.1"}]}],"bundled":41},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.1-160000.6.1"}]}],"bundled":41},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.1-160000.6.1"}]}],"bundled":41},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-150400.3.34.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-150600.3.24.1"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-150600.3.24.1"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.7-150600.3.24.1"}]}],"bundled":33},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.0.9-4ubuntu1","3.1.0-2","3.1.0-2ubuntu0.1","3.1.0-2ubuntu0.2","3.1.0-2ubuntu0.3","3.1.0-2ubuntu0.4","3.1.0-2ubuntu0.4+esm1","3.1.0-2ubuntu0.4+esm2","3.1.0-2ubuntu0.4+esm3","3.1.0-2ubuntu0.4+esm4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.1-3","3.1.1-3ubuntu1","3.1.1-3ubuntu1.1","3.1.1-3ubuntu1.2","3.1.1-3ubuntu1.3","3.1.1-3ubuntu1.3+esm1","3.1.1-3ubuntu1.3+esm2","3.1.1-3ubuntu1.3+esm3","3.1.1-3ubuntu1.3+esm4","3.1.1-3ubuntu1.3+esm5","3.1.1-3ubuntu1.3+esm6"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.2-2","3.1.2-2.1","3.1.2-2.1ubuntu1","3.1.2-2.1ubuntu1.1","3.1.2-2.1ubuntu1.2","3.1.2-2.1ubuntu1.3","3.1.2-2.1ubuntu1.4","3.1.2-2.1ubuntu1.5","3.1.2-2.1ubuntu1.6","3.1.2-2.1ubuntu1.6+esm1","3.1.2-2.1ubuntu1.6+esm2","3.1.2-2.1ubuntu1.6+esm3","3.1.2-2.1ubuntu1.6+esm4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.3-6","3.1.3-8","3.1.3-8ubuntu0.1","3.1.3-8ubuntu0.2","3.1.3-8ubuntu0.3","3.1.3-8ubuntu0.4","3.1.3-8ubuntu0.5","3.1.3-8ubuntu0.7","3.1.3-8ubuntu0.8","3.1.3-8ubuntu0.9","3.1.3-8ubuntu0.9+esm1","3.1.3-8ubuntu0.9+esm2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.2.3-4ubuntu1","3.2.3-4ubuntu2","3.2.3-8ubuntu1","3.2.3-8ubuntu2","3.2.3-8ubuntu3","3.2.3-8ubuntu3.1","3.2.7-0ubuntu0.22.04.2","3.2.7-0ubuntu0.22.04.3","3.2.7-0ubuntu0.22.04.4","3.2.7-0ubuntu0.22.04.6","3.2.7-0ubuntu0.22.04.7"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.2.7-1","3.2.7-1build1","3.2.7-1build2","3.2.7-1ubuntu1","3.2.7-1ubuntu1.1","3.2.7-1ubuntu1.2","3.2.7-1ubuntu1.4","3.2.7-1ubuntu1.5"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.4.1+ds1-7","3.4.4+ds1-1","3.4.4+ds1-1build1","3.5.0+ds1-2"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.4.1+ds1-5ubuntu1","3.4.1+ds1-6","3.4.1+ds1-7","3.4.1+ds1-7ubuntu0.2","3.4.1+ds1-7ubuntu0.3"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.1-1.1"}]}],"bundled":37},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"rsync","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.1-160000.6.1"}]}],"bundled":41}],"products":[{"vendor":"rsyncproject","product":"rsync"},{"vendor":"samba","product":"rsync"}],"references":[{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-gg3m-4m9m-268h","tags":["vendor-advisory","Vendor Advisory","advisory","article"]},{"url":"https://github.com/RsyncProject/rsync/releases/tag/v3.5.0","tags":["release-notes","Release Notes","advisory","article"]},{"url":"https://www.vulncheck.com/advisories/rsync-out-of-bounds-write-via-flag-hlinked-handling","tags":["third-party-advisory","Third Party Advisory","advisory","article"]},{"url":"https://security.alpinelinux.org/vuln/CVE-2026-70458","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:67462","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53783","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53784","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53785","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53789","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53790","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53791","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53793","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53795","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53802","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-53803","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70452","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70453","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70454","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70456","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70457","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70458","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70460","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70461","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70463","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70464","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515368","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515373","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515378","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515379","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515380","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515381","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515384","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515385","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515386","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515387","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515389","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515395","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515396","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515403","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515409","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515417","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515419","tags":["report"]},{"url":"https://errata.almalinux.org/9/ALSA-2026-67462.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:67463","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-70455","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515406","tags":["report"]},{"url":"https://errata.almalinux.org/10/ALSA-2026-67463.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:74095","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/2515375","tags":["report"]},{"url":"https://bugzilla.redhat.com/2515416","tags":["report"]},{"url":"https://errata.almalinux.org/8/ALSA-2026-74095.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70458","tags":["web","advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-70458","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/debian10els/CLSA-2026-1788335736.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53789","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53790","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53792","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70453","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70456","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70459","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70461","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70463","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70464","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu16.04els/CLSA-2026-1789662743.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53793","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/rhel7els/CLSA-2026-1789730480.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu20.04els/CLSA-2026-1789735848.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/oraclelinux7els/CLSA-2026-1789737420.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1789737518.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53794","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/centos7els/CLSA-2026-1789749013.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1789783256.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/centos8.5els/CLSA-2026-1790173668.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/centos-stream8els/CLSA-2026-1790267010.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53783","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/oraclelinux6els/CLSA-2026-1791331076.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/centos6els/CLSA-2026-1791331932.html","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/70xxx/CVE-2026-70458.json","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-70458","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0487.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36138","tags":["report"]},{"url":"https://www.openwall.com/lists/oss-security/2026/08/13/1","tags":["web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AHYZL7IBFVF463AGDTJUQBYUJUW7JUAB/","tags":["web"]},{"url":"https://lists.debian.org/debian-security-announce/2026/msg00440.html","tags":["web"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3949","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53784","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53788","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53797","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53799","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53802","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70454","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70457","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70460","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3950","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4072","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515368","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515373","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515375","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515378","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515379","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515380","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515381","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515384","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515385","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515386","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515387","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515389","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515395","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515396","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515403","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515407","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515409","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515416","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515417","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515419","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_67462.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53783","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-9cgc-64g4-3gv5","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-toctou-race-condition-directory-escape-via-rrsync","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53784","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-ffg2-fr5g-3rxw","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-path-traversal-via-symlink-module-root","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53785","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-pph3-7xmf-rrqg","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-path-traversal-write-escape-via-relative-mode","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53789","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-fxwg-7hmf-xh5q","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-arbitrary-file-deletion-via-malicious-file-list","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53790","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-5hcf-7xxm-rmqq","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-command-injection-via-multiple-code-paths","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53791","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-h2q9-5fr8-w635","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-daemon-ip-spoofing-via-proxy-protocol-header","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53793","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-wj7w-vh23-mm44","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-path-confinement-bypass-via-boundary-marker-in-chroot-mode","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53795","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-m9vj-637x-v6pq","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-arbitrary-file-write-via-temp-dir-link-dest","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53802","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-4mfr-8jrv-49x4","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-arbitrary-file-read-via-symlink-following","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53803","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-g9f4-7q66-9582","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-symlink-following-arbitrary-file-overwrite","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70452","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-6692-28cx-wpqq","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-access-control-bypass-via-dns-resolution-failure","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70453","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-8x5r-mjx8-83hv","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-algorithmic-complexity-dos-via-hash-search","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70454","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-3c3x-ww2w-5r5p","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-tls-certificate-validation-bypass-via-ssl-openssl-mode","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70456","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-78jc-79jv-v6rw","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-heap-out-of-bounds-write-via-read-args","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70457","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-pg7g-xqmr-xpfh","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-out-of-bounds-write-via-parse-size-arg","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70458","tags":["advisory","report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70460","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-w3xf-j2r2-gv4x","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-path-traversal-via-partial-dir-backup-dir-symlink","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70461","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-jhxm-j4mq-3fj4","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-heap-out-of-bounds-write-via-files-from-entry","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70463","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-pfj8-79vq-xgvr","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-authorization-bypass-via-auth-users-directive-parsing","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70464","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-hrwq-ccf7-rw5m","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-connection-slot-exhaustion-dos-via-handshake-stall","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2515406","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_67463.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-70455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-70455","tags":["advisory"]},{"url":"https://github.com/RsyncProject/rsync/security/advisories/GHSA-rjvj-qgqg-cvx9","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/rsync-dos-via-zt-zstandard-compression-thread-exhaustion","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_74095.json","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2026:67462","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2026:67463","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2026:74095","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623253-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1269039","tags":["report"]},{"url":"https://bugzilla.suse.com/1269040","tags":["report"]},{"url":"https://bugzilla.suse.com/1269041","tags":["report"]},{"url":"https://bugzilla.suse.com/1269042","tags":["report"]},{"url":"https://bugzilla.suse.com/1269043","tags":["report"]},{"url":"https://bugzilla.suse.com/1269044","tags":["report"]},{"url":"https://bugzilla.suse.com/1269045","tags":["report"]},{"url":"https://bugzilla.suse.com/1269046","tags":["report"]},{"url":"https://bugzilla.suse.com/1269047","tags":["report"]},{"url":"https://bugzilla.suse.com/1269048","tags":["report"]},{"url":"https://bugzilla.suse.com/1269049","tags":["report"]},{"url":"https://bugzilla.suse.com/1269050","tags":["report"]},{"url":"https://bugzilla.suse.com/1269051","tags":["report"]},{"url":"https://bugzilla.suse.com/1269052","tags":["report"]},{"url":"https://bugzilla.suse.com/1269053","tags":["report"]},{"url":"https://bugzilla.suse.com/1269054","tags":["report"]},{"url":"https://bugzilla.suse.com/1269055","tags":["report"]},{"url":"https://bugzilla.suse.com/1269056","tags":["report"]},{"url":"https://bugzilla.suse.com/1269057","tags":["report"]},{"url":"https://bugzilla.suse.com/1269058","tags":["report"]},{"url":"https://bugzilla.suse.com/1269060","tags":["report"]},{"url":"https://bugzilla.suse.com/1273429","tags":["report"]},{"url":"https://bugzilla.suse.com/1273430","tags":["report"]},{"url":"https://bugzilla.suse.com/1273431","tags":["report"]},{"url":"https://bugzilla.suse.com/1273432","tags":["report"]},{"url":"https://bugzilla.suse.com/1273433","tags":["report"]},{"url":"https://bugzilla.suse.com/1273434","tags":["report"]},{"url":"https://bugzilla.suse.com/1273435","tags":["report"]},{"url":"https://bugzilla.suse.com/1273436","tags":["report"]},{"url":"https://bugzilla.suse.com/1273437","tags":["report"]},{"url":"https://bugzilla.suse.com/1273438","tags":["report"]},{"url":"https://bugzilla.suse.com/1273439","tags":["report"]},{"url":"https://bugzilla.suse.com/1273440","tags":["report"]},{"url":"https://bugzilla.suse.com/1273441","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43617","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43618","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43620","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53796","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-70464","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623254-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623289-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1271931","tags":["report"]},{"url":"https://bugzilla.suse.com/1271932","tags":["report"]},{"url":"https://bugzilla.suse.com/1271933","tags":["report"]},{"url":"https://bugzilla.suse.com/1271934","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-44507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-44508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-44509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-44510","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623323-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263634-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1264514","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-41035","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263657-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-70458","tags":["report"]},{"url":"https://download.samba.org/pub/rsync/NEWS#3.5.0","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-70458","title":"rsync 3.0.0 \u003c 3.5.0 Out-of-Bounds Write via FLAG_HLINKED Handling","description":"rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.","status":"published","published":"2026-08-13T14:44:06.034Z","modified":"2026-08-14T16:51:22.283Z","cvss":[{"version":"4.0","score":8.8,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","level":"high","assessor":"cna"},{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high","assessor":"cna"}],"cwes":["CWE-787"],"updated_at":"2026-11-02T13:35:22.169514Z"}],"euvd":[{"id":"EUVD-2026-58046","description":"rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.","status":"published","published":"2026-08-13T14:44:06Z","modified":"2026-08-14T16:51:22Z","cvss":[{"version":"4.0","score":8.8,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","level":"high"}],"updated_at":"2026-11-02T18:01:54.232317Z"}],"nvd":[{"id":"CVE-2026-70458","description":"rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.","status":"published","published":"2026-08-13T15:19:59.663Z","modified":"2026-11-06T15:58:17.48Z","cvss":[{"version":"4.0","score":8.8,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"},{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-787"],"updated_at":"2026-11-06T18:00:52.991057Z"}],"osv":[{"id":"ALPINE-CVE-2026-70458","description":"rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.","status":"published","published":"2026-08-13T15:19:59.663Z","modified":"2026-11-07T09:30:03.890993715Z","cvss":[{"version":"4.0","score":8.8,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high"}],"updated_at":"2026-11-07T09:42:35.936113Z"},{"id":"BELL-CVE-2026-70458","status":"published","published":"2026-08-15T06:06:33.578494Z","modified":"2026-09-25T07:15:03.629361701Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:25.50888Z"},{"id":"CVE-2026-70458","title":"rsync 3.0.0 \u003c 3.5.0 Out-of-Bounds Write via FLAG_HLINKED Handling","description":"rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.","status":"published","published":"2026-08-13T14:44:06.034Z","modified":"2026-11-08T02:47:41.393591799Z","cvss":[{"version":"4.0","score":8.8,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-787"],"updated_at":"2026-11-08T03:29:52.421856Z"},{"id":"DEBIAN-CVE-2026-70458","description":"rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.","status":"published","published":"2026-08-13T15:19:59.663Z","modified":"2026-11-09T05:00:10.154146713Z","cvss":[{"version":"4.0","score":8.8,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high"}],"updated_at":"2026-11-09T05:19:10.514151Z"},{"id":"OESA-2026-3949","title":"rsync security update","description":"Rsync is an open source utility that provides fast incremental file transfer. It uses the \u0026amp;quot;rsync algorithm\u0026amp;quot; which provides a very fast method for bringing remote files into sync. It does this by sending just the differences in the files across the link, without requiring that both sets of files are present at one of the ends of the link beforehand.\r\n\r\nSecurity Fix(es):\n\nRsync version 3.4.2 and prior contain symlink race condition vulnerabilities in path-based system calls including chmod, lchown, utimes, rename, unlink, mkdir, symlink, mknod, link, rmdir, and lstat that allow local attackers to redirect operations to files outside the exported rsync module. Attackers with local filesystem access can exploit the timing window between path resolution and syscall execution by swapping symlinks to apply sender-supplied permissions, ownership, timestamps, or filenames to arbitrary files outside the intended module boundary on rsync daemons configured with \u0026apos;use chroot = no\u0026apos;.(CVE-2026-43619)\n\nrsync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the rrsync restricted shell wrapper that allows authenticated clients to escape enforced directory restrictions by substituting a symlink for a path component after validation but before transfer processing. Attackers can additionally leverage unrestricted flags such as --copy-unsafe-links, -D, and --log-file through rrsync to read or write files outside the permitted directory subtree.(CVE-2026-53783)\n\nrsync before 3.5.0 contains a path traversal vulnerability that allows remote clients to access files outside the intended module root when use chroot is disabled and the module root path or a component of it is a symlink. The daemon calls chdir() to the module root at session initialization without resolving symlinks via realpath() or equivalent, causing subsequent relative-path operations to reference files relative to the symlink target rather than the intended module root, enabling unauthorized file access.(CVE-2026-53784)\n\nrsync before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to write files outside the intended destination directory tree by crafting relative paths with symlink components in --relative mode. The make_path() function follows symlinks pointing outside the destination tree while creating intermediate directories without verifying that created paths remain within the destination boundary, enabling arbitrary file writes on the receiver\u0026apos;s filesystem.(CVE-2026-53785)\n\nrsync before 3.5.0 contains a filter rule bypass vulnerability that allows authenticated clients to override module-level filter restrictions by supplying malicious --filter merge file directives. Attackers can inject client-side merge file directives during filter evaluation to introduce rules that supersede daemon module-level restrictions, gaining access to files the module filter was intended to exclude.(CVE-2026-53786)\n\nrsync before 3.5.0 contains a newline injection vulnerability in the name-converter uid/gid mapping interface that allows local attackers to forge protocol messages by creating user or group names containing newline characters. Attackers can inject malicious newline characters into names communicated over the pipe-based line-oriented protocol to cause the rsync daemon to process attacker-influenced data as legitimate protocol input, corrupting uid/gid mapping logic.(CVE-2026-53788)\n\nrsync before 3.5.0 contains an improper path handling vulnerability that allows a malicious sender to expand the scope of --delete operations beyond the intended destination subtree by sending a crafted file list that causes rsync to reclassify implied parent directory entries or treat synthetic paths as the transfer root. Attackers can exploit multiple variants including implied parent reclassification, synthetic root path construction, legacy protocol behavior below version 30, and non-directory root handling to cause the receiver to delete files outside the authorized destination directory.(CVE-2026-53789)\n\nrsync before 3.5.0 contains multiple command and argument injection vulnerabilities that allow attackers to execute arbitrary commands by supplying malicious input through several code paths, including the RSYNC_CONNECT_PROG environment variable, daemon hooks, the rsync-ssl wrapper, and remote-shell command newline injection. Attackers can inject shell metacharacters or newline characters into unsanitized user-supplied values such as hostnames and hostspecs to execute arbitrary commands under the privileges of the rsync process or the invoking user.(CVE-2026-53790)\n\nrsync daemon before 3.5.0 contains an IP address spoofing vulnerability that allows unauthenticated remote attackers to bypass IP-based access controls by sending a crafted PROXY protocol header with a forged source address. Attackers who can connect directly to the rsync daemon can inject a spoofed source IP in the PROXY protocol header to circumvent hosts allow/deny rules, gaining unauthorized access that would otherwise be blocked based on their real source address.(CVE-2026-53791)\n\nrsync before 3.5.0 contains an out-of-bounds read vulnerability in the sender-side block matching logic that allows a malicious receiver to trigger memory access before the start of an allocated buffer by sending a crafted checksum block with a length of zero. Attackers can send a specially crafted checksum set containing a zero-length block to cause a negative offset calculation during delta computation, resulting in an out-of-bounds read of file data buffer memory on the sender side.(CVE-2026-53792)\n\nrsync before 3.5.0 contains a path confinement bypass vulnerability that allows remote clients to escape the intended inner-module root confinement by constructing paths that resolve outside the chroot boundary when the module root contains a /./ boundary marker. Attackers can exploit improper handling of the /./ notation or forge delta-basis transfers referencing xname paths that cross the /./ boundary to gain unauthorized read or write access to files outside the module\u0026apos;s subtree.(CVE-2026-53793)\n\nrsync before 3.5.0 contains a logic error in --max-alloc handling that allows a sender or configuration setting --max-alloc=0 to disable allocation sanity checks entirely rather than enforcing a zero-byte cap. Attackers can exploit this flaw to cause the receiver to attempt unbounded memory allocations for file list and data structures, potentially exhausting available memory and causing a denial of service.(CVE-2026-53794)\n\nrsync before 3.5.0 contains an arbitrary file write vulnerability that allows attackers to write files outside the intended destination tree by specifying an absolute path via --temp-dir or --link-dest options. The rename-confinement logic is bypassed when these options resolve to paths outside the destination tree, enabling attacker-controlled values to write files to arbitrary locations accessible to the rsync process.(CVE-2026-53795)\n\nrsync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the non-daemon receiver\u0026apos;s destination directory handling that allows an attacker who can manipulate destination path parent components to redirect file writes to unintended locations. Attackers can substitute a symlink for a component of the destination path between the path resolution and chdir() call, causing the receiver\u0026apos;s working directory to be established outside the intended destination tree so that subsequent relative-path file writes land in unintended filesystem locations.(CVE-2026-53796)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability in the sender\u0026apos;s source tree traversal that allows an attacker who can manipulate a parent directory of the source tree to redirect file reads to unintended paths. Attackers can atomically replace a parent directory component with a symlink pointing outside the source root between path resolution and file open operations to disclose file contents outside the intended transfer root.(CVE-2026-53797)\n\nrsync before 3.5.0 contains a privilege confusion vulnerability in the name-converter subprocess uid/gid mapping that allows local attackers to cause transferred files to be owned by root by influencing name-converter responses to return empty values. When the name-converter subprocess returns an empty response for a uid or gid lookup, rsync incorrectly interprets it as a successful resolution to uid/gid 0 (root) rather than a lookup failure, and if the name-converter also signals fake super-user status, rsync proceeds with root ownership assignments for transferred files.(CVE-2026-53798)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability that allows local attackers to cause rsync to apply arbitrary ACLs or extended attributes to unintended files by substituting a symlink at a predictable destination path between the file write and the subsequent acl_set_file() or lsetxattr() call. Attackers can exploit this timing window to redirect ACL and xattr application through a crafted symlink to files outside the intended destination tree, potentially granting elevated permissions and enabling local privilege escalation.(CVE-2026-53799)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability in the --remove-source-files feature that allows attackers with symlink creation access to cause arbitrary file deletion. Attackers can atomically substitute a symlink for a source file between transfer completion and the unlink() call, causing rsync to delete the symlink target rather than the intended source file.(CVE-2026-53800)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability in the sender\u0026apos;s directory scanning logic that allows attackers to cause the sender to enumerate and transfer files outside the module root\u0026apos;s intended subtree. Attackers who can create or manipulate symlinks in a path component of the scanned tree can replace a symlink with a directory entry pointing outside the module root between the lstat() call and the subsequent opendir() call, exposing files beyond the intended root in both daemon-mode and non-daemon sender-side scanning.(CVE-2026-53801)\n\nrsync before 3.5.0 contains an arbitrary file read vulnerability that allows attackers to read files accessible to the rsync daemon process by exploiting symlink following in input configuration file handling including --files-from, --password-file, and filter merge files. Attackers can place a symlink at a predictable --files-from or --password-file path, or supply a --files-from path that escapes the daemon module root, to read arbitrary files accessible to the rsync process.(CVE-2026-53802)\n\nrsync before 3.5.0 contains a symlink following vulnerability that allows local attackers to overwrite arbitrary files by placing a symlink at a predictable output path such as --log-file, --write-batch, or daemon-mode log and statistics paths. Attackers can exploit rsync\u0026apos;s failure to reject symlinks during ancillary file writes to redirect output to arbitrary filesystem locations, achieving local privilege escalation on installations where rsync runs with elevated privileges such as setuid or privileged daemon configurations.(CVE-2026-53803)\n\nrsync 3.1.0 before 3.5.0 contains an access control bypass vulnerability that allows remote attackers to circumvent hosts deny rules by inducing DNS resolution failures during hostname-based access control evaluation. When a DNS lookup for a hostname-based deny rule fails, the daemon skips the rule rather than defaulting to a deny decision, enabling attackers who can trigger DNS failures to bypass module-level IP access controls and gain unauthorized access to restricted module file trees.(CVE-2026-70452)\n\nrsync before 3.5.0 contains an algorithmic complexity vulnerability in the hash_search() function that allows a remote attacker to cause a denial of service by delivering a carefully constructed file list. A sender can exploit the quadratic-time worst-case behavior in hash lookups to exhaust receiver CPU resources with a modest number of crafted entries, causing a sustained denial of service.(CVE-2026-70453)\n\nrsync 3.2.0 through 3.2.3 (openssl mode) and rsync-ssl through 3.4.4 (stunnel mode) contain a TLS certificate validation vulnerability that allows on-path attackers to intercept encrypted sessions by presenting self-signed or otherwise invalid certificates. Attackers can exploit the failure to validate server TLS certificates against a trusted CA or verify certificate hostname matching to decrypt or tamper with rsync session content without detection by the client.(CVE-2026-70454)\n\nrsync 3.0.1 before 3.5.0 contains an out-of-bounds write vulnerability in the read_args() function that allows a malicious sender to corrupt adjacent heap memory by sending a crafted argument list. When the argument count causes the argv allocation to be exactly full, the trailing NULL terminator is written one slot beyond the allocation boundary, corrupting adjacent heap memory.(CVE-2026-70456)\n\nrsync 3.2.3 before 3.5.0 contains an out-of-bounds write in parse_size_arg() where the return value of snprintf() is used directly as an index into a .bss-segment array without bounds checking. When snprintf truncates the formatted size string, the return value equals the number of characters that would have been written including the truncated portion, and this value may exceed the array length. The subsequent indexed write targets memory outside the intended array bounds, corrupting .bss memory.(CVE-2026-70457)\n\nrsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.(CVE-2026-70458)\n\nrsync 3.0.0 before 3.5.0 contains a null pointer dereference vulnerability in the daemon child process that allows remote attackers to crash the daemon by sending a file list whose first entry is a dot entry not typed as a directory. The daemon dereferences the first file list entry as a directory structure pointer without verifying the entry type, resulting in an invalid or uninitialized pointer dereference that terminates the client connection.(CVE-2026-70459)\n\nrsync 2.3.3 before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to escape the module root by exploiting symlinks within the module file tree when using --partial-dir or --backup-dir options. Attackers with write access to place a symlink under the module root, or who can exploit a pre-existing trusted symlink, can direct file writes to locations outside the intended module root, achieving arbitrary file write relative to the module root parent.(CVE-2026-70460)\n\nrsync 3.2.5 before 3.5.0 contains a heap out-of-bounds write vulnerability that allows remote unauthenticated attackers to write one attacker-controlled byte past the end of a heap allocation by supplying a crafted files-from entry. Attackers can trigger the vulnerability against a read-only rsync daemon module by providing a files-from entry containing both an interior and trailing backslash, causing the add_implied_include() function to under-count the trailing backslash when sizing the destination buffer.(CVE-2026-70461)\n\nrsync 3.1.0 before 3.5.0 contains a signed integer overflow vulnerability in the I/O timeout implementation that allows attackers to permanently disable connection timeouts by injecting MSG_IO_TIMEOUT messages carrying non-positive (zero or negative) values. Attackers can craft malicious MSG_IO_TIMEOUT messages that cause the timeout variable to wrap to a non-positive value, preventing the timeout check from firing and enabling idle or stalled connections to hold daemon slots indefinitely, leading to resource exhaustion.(CVE-2026-70462)\n\nrsync 3.1.0 before 3.5.0 contains an authorization bypass in auth users directive parsing. The auth users parser uses comma-only tokenization when splitting the user list, which fails to correctly handle entries of the form @Group Name where the group name contains a space. The space within the group name causes the parser to split the entry at the space boundary, discarding the deny rule associated with the group. An authenticated user whose username or group membership would be denied by an @Group Name auth users entry can connect to a restricted module because the deny rule is silently discarded during parsing.(CVE-2026-70463)\n\nrsync daemon 2.0.0 before 3.5.0 contains a denial of service vulnerability that allows unauthenticated remote attackers to exhaust daemon connection slots by stalling the handshake process before or after module selection without triggering the I/O timeout. Attackers can open many simultaneous connections and trickle data at the minimum rate to avoid timeout, or stall entirely before module selection where no timeout applies, consuming all available connection slots and denying service to legitimate clients.(CVE-2026-70464)","status":"published","published":"2026-09-20T13:23:30Z","modified":"2026-09-20T13:30:30.302568447Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:52:47.643553Z"},{"id":"OESA-2026-3950","title":"rsync security update","description":"Rsync is an open source utility that provides fast incremental file transfer. It uses the \u0026amp;quot;rsync algorithm\u0026amp;quot; which provides a very fast method for bringing remote files into sync. It does this by sending just the differences in the files across the link, without requiring that both sets of files are present at one of the ends of the link beforehand.\r\n\r\nSecurity Fix(es):\n\nRsync version 3.4.2 and prior contain symlink race condition vulnerabilities in path-based system calls including chmod, lchown, utimes, rename, unlink, mkdir, symlink, mknod, link, rmdir, and lstat that allow local attackers to redirect operations to files outside the exported rsync module. Attackers with local filesystem access can exploit the timing window between path resolution and syscall execution by swapping symlinks to apply sender-supplied permissions, ownership, timestamps, or filenames to arbitrary files outside the intended module boundary on rsync daemons configured with \u0026apos;use chroot = no\u0026apos;.(CVE-2026-43619)\n\nrsync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the rrsync restricted shell wrapper that allows authenticated clients to escape enforced directory restrictions by substituting a symlink for a path component after validation but before transfer processing. Attackers can additionally leverage unrestricted flags such as --copy-unsafe-links, -D, and --log-file through rrsync to read or write files outside the permitted directory subtree.(CVE-2026-53783)\n\nrsync before 3.5.0 contains a path traversal vulnerability that allows remote clients to access files outside the intended module root when use chroot is disabled and the module root path or a component of it is a symlink. The daemon calls chdir() to the module root at session initialization without resolving symlinks via realpath() or equivalent, causing subsequent relative-path operations to reference files relative to the symlink target rather than the intended module root, enabling unauthorized file access.(CVE-2026-53784)\n\nrsync before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to write files outside the intended destination directory tree by crafting relative paths with symlink components in --relative mode. The make_path() function follows symlinks pointing outside the destination tree while creating intermediate directories without verifying that created paths remain within the destination boundary, enabling arbitrary file writes on the receiver\u0026apos;s filesystem.(CVE-2026-53785)\n\nrsync before 3.5.0 contains a filter rule bypass vulnerability that allows authenticated clients to override module-level filter restrictions by supplying malicious --filter merge file directives. Attackers can inject client-side merge file directives during filter evaluation to introduce rules that supersede daemon module-level restrictions, gaining access to files the module filter was intended to exclude.(CVE-2026-53786)\n\nrsync before 3.5.0 contains a newline injection vulnerability in the name-converter uid/gid mapping interface that allows local attackers to forge protocol messages by creating user or group names containing newline characters. Attackers can inject malicious newline characters into names communicated over the pipe-based line-oriented protocol to cause the rsync daemon to process attacker-influenced data as legitimate protocol input, corrupting uid/gid mapping logic.(CVE-2026-53788)\n\nrsync before 3.5.0 contains an improper path handling vulnerability that allows a malicious sender to expand the scope of --delete operations beyond the intended destination subtree by sending a crafted file list that causes rsync to reclassify implied parent directory entries or treat synthetic paths as the transfer root. Attackers can exploit multiple variants including implied parent reclassification, synthetic root path construction, legacy protocol behavior below version 30, and non-directory root handling to cause the receiver to delete files outside the authorized destination directory.(CVE-2026-53789)\n\nrsync before 3.5.0 contains multiple command and argument injection vulnerabilities that allow attackers to execute arbitrary commands by supplying malicious input through several code paths, including the RSYNC_CONNECT_PROG environment variable, daemon hooks, the rsync-ssl wrapper, and remote-shell command newline injection. Attackers can inject shell metacharacters or newline characters into unsanitized user-supplied values such as hostnames and hostspecs to execute arbitrary commands under the privileges of the rsync process or the invoking user.(CVE-2026-53790)\n\nrsync daemon before 3.5.0 contains an IP address spoofing vulnerability that allows unauthenticated remote attackers to bypass IP-based access controls by sending a crafted PROXY protocol header with a forged source address. Attackers who can connect directly to the rsync daemon can inject a spoofed source IP in the PROXY protocol header to circumvent hosts allow/deny rules, gaining unauthorized access that would otherwise be blocked based on their real source address.(CVE-2026-53791)\n\nrsync before 3.5.0 contains an out-of-bounds read vulnerability in the sender-side block matching logic that allows a malicious receiver to trigger memory access before the start of an allocated buffer by sending a crafted checksum block with a length of zero. Attackers can send a specially crafted checksum set containing a zero-length block to cause a negative offset calculation during delta computation, resulting in an out-of-bounds read of file data buffer memory on the sender side.(CVE-2026-53792)\n\nrsync before 3.5.0 contains a path confinement bypass vulnerability that allows remote clients to escape the intended inner-module root confinement by constructing paths that resolve outside the chroot boundary when the module root contains a /./ boundary marker. Attackers can exploit improper handling of the /./ notation or forge delta-basis transfers referencing xname paths that cross the /./ boundary to gain unauthorized read or write access to files outside the module\u0026apos;s subtree.(CVE-2026-53793)\n\nrsync before 3.5.0 contains a logic error in --max-alloc handling that allows a sender or configuration setting --max-alloc=0 to disable allocation sanity checks entirely rather than enforcing a zero-byte cap. Attackers can exploit this flaw to cause the receiver to attempt unbounded memory allocations for file list and data structures, potentially exhausting available memory and causing a denial of service.(CVE-2026-53794)\n\nrsync before 3.5.0 contains an arbitrary file write vulnerability that allows attackers to write files outside the intended destination tree by specifying an absolute path via --temp-dir or --link-dest options. The rename-confinement logic is bypassed when these options resolve to paths outside the destination tree, enabling attacker-controlled values to write files to arbitrary locations accessible to the rsync process.(CVE-2026-53795)\n\nrsync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the non-daemon receiver\u0026apos;s destination directory handling that allows an attacker who can manipulate destination path parent components to redirect file writes to unintended locations. Attackers can substitute a symlink for a component of the destination path between the path resolution and chdir() call, causing the receiver\u0026apos;s working directory to be established outside the intended destination tree so that subsequent relative-path file writes land in unintended filesystem locations.(CVE-2026-53796)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability in the sender\u0026apos;s source tree traversal that allows an attacker who can manipulate a parent directory of the source tree to redirect file reads to unintended paths. Attackers can atomically replace a parent directory component with a symlink pointing outside the source root between path resolution and file open operations to disclose file contents outside the intended transfer root.(CVE-2026-53797)\n\nrsync before 3.5.0 contains a privilege confusion vulnerability in the name-converter subprocess uid/gid mapping that allows local attackers to cause transferred files to be owned by root by influencing name-converter responses to return empty values. When the name-converter subprocess returns an empty response for a uid or gid lookup, rsync incorrectly interprets it as a successful resolution to uid/gid 0 (root) rather than a lookup failure, and if the name-converter also signals fake super-user status, rsync proceeds with root ownership assignments for transferred files.(CVE-2026-53798)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability that allows local attackers to cause rsync to apply arbitrary ACLs or extended attributes to unintended files by substituting a symlink at a predictable destination path between the file write and the subsequent acl_set_file() or lsetxattr() call. Attackers can exploit this timing window to redirect ACL and xattr application through a crafted symlink to files outside the intended destination tree, potentially granting elevated permissions and enabling local privilege escalation.(CVE-2026-53799)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability in the --remove-source-files feature that allows attackers with symlink creation access to cause arbitrary file deletion. Attackers can atomically substitute a symlink for a source file between transfer completion and the unlink() call, causing rsync to delete the symlink target rather than the intended source file.(CVE-2026-53800)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability in the sender\u0026apos;s directory scanning logic that allows attackers to cause the sender to enumerate and transfer files outside the module root\u0026apos;s intended subtree. Attackers who can create or manipulate symlinks in a path component of the scanned tree can replace a symlink with a directory entry pointing outside the module root between the lstat() call and the subsequent opendir() call, exposing files beyond the intended root in both daemon-mode and non-daemon sender-side scanning.(CVE-2026-53801)\n\nrsync before 3.5.0 contains an arbitrary file read vulnerability that allows attackers to read files accessible to the rsync daemon process by exploiting symlink following in input configuration file handling including --files-from, --password-file, and filter merge files. Attackers can place a symlink at a predictable --files-from or --password-file path, or supply a --files-from path that escapes the daemon module root, to read arbitrary files accessible to the rsync process.(CVE-2026-53802)\n\nrsync before 3.5.0 contains a symlink following vulnerability that allows local attackers to overwrite arbitrary files by placing a symlink at a predictable output path such as --log-file, --write-batch, or daemon-mode log and statistics paths. Attackers can exploit rsync\u0026apos;s failure to reject symlinks during ancillary file writes to redirect output to arbitrary filesystem locations, achieving local privilege escalation on installations where rsync runs with elevated privileges such as setuid or privileged daemon configurations.(CVE-2026-53803)\n\nrsync 3.1.0 before 3.5.0 contains an access control bypass vulnerability that allows remote attackers to circumvent hosts deny rules by inducing DNS resolution failures during hostname-based access control evaluation. When a DNS lookup for a hostname-based deny rule fails, the daemon skips the rule rather than defaulting to a deny decision, enabling attackers who can trigger DNS failures to bypass module-level IP access controls and gain unauthorized access to restricted module file trees.(CVE-2026-70452)\n\nrsync before 3.5.0 contains an algorithmic complexity vulnerability in the hash_search() function that allows a remote attacker to cause a denial of service by delivering a carefully constructed file list. A sender can exploit the quadratic-time worst-case behavior in hash lookups to exhaust receiver CPU resources with a modest number of crafted entries, causing a sustained denial of service.(CVE-2026-70453)\n\nrsync 3.2.0 through 3.2.3 (openssl mode) and rsync-ssl through 3.4.4 (stunnel mode) contain a TLS certificate validation vulnerability that allows on-path attackers to intercept encrypted sessions by presenting self-signed or otherwise invalid certificates. Attackers can exploit the failure to validate server TLS certificates against a trusted CA or verify certificate hostname matching to decrypt or tamper with rsync session content without detection by the client.(CVE-2026-70454)\n\nrsync 3.0.1 before 3.5.0 contains an out-of-bounds write vulnerability in the read_args() function that allows a malicious sender to corrupt adjacent heap memory by sending a crafted argument list. When the argument count causes the argv allocation to be exactly full, the trailing NULL terminator is written one slot beyond the allocation boundary, corrupting adjacent heap memory.(CVE-2026-70456)\n\nrsync 3.2.3 before 3.5.0 contains an out-of-bounds write in parse_size_arg() where the return value of snprintf() is used directly as an index into a .bss-segment array without bounds checking. When snprintf truncates the formatted size string, the return value equals the number of characters that would have been written including the truncated portion, and this value may exceed the array length. The subsequent indexed write targets memory outside the intended array bounds, corrupting .bss memory.(CVE-2026-70457)\n\nrsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.(CVE-2026-70458)\n\nrsync 3.0.0 before 3.5.0 contains a null pointer dereference vulnerability in the daemon child process that allows remote attackers to crash the daemon by sending a file list whose first entry is a dot entry not typed as a directory. The daemon dereferences the first file list entry as a directory structure pointer without verifying the entry type, resulting in an invalid or uninitialized pointer dereference that terminates the client connection.(CVE-2026-70459)\n\nrsync 2.3.3 before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to escape the module root by exploiting symlinks within the module file tree when using --partial-dir or --backup-dir options. Attackers with write access to place a symlink under the module root, or who can exploit a pre-existing trusted symlink, can direct file writes to locations outside the intended module root, achieving arbitrary file write relative to the module root parent.(CVE-2026-70460)\n\nrsync 3.2.5 before 3.5.0 contains a heap out-of-bounds write vulnerability that allows remote unauthenticated attackers to write one attacker-controlled byte past the end of a heap allocation by supplying a crafted files-from entry. Attackers can trigger the vulnerability against a read-only rsync daemon module by providing a files-from entry containing both an interior and trailing backslash, causing the add_implied_include() function to under-count the trailing backslash when sizing the destination buffer.(CVE-2026-70461)\n\nrsync 3.1.0 before 3.5.0 contains a signed integer overflow vulnerability in the I/O timeout implementation that allows attackers to permanently disable connection timeouts by injecting MSG_IO_TIMEOUT messages carrying non-positive (zero or negative) values. Attackers can craft malicious MSG_IO_TIMEOUT messages that cause the timeout variable to wrap to a non-positive value, preventing the timeout check from firing and enabling idle or stalled connections to hold daemon slots indefinitely, leading to resource exhaustion.(CVE-2026-70462)\n\nrsync 3.1.0 before 3.5.0 contains an authorization bypass in auth users directive parsing. The auth users parser uses comma-only tokenization when splitting the user list, which fails to correctly handle entries of the form @Group Name where the group name contains a space. The space within the group name causes the parser to split the entry at the space boundary, discarding the deny rule associated with the group. An authenticated user whose username or group membership would be denied by an @Group Name auth users entry can connect to a restricted module because the deny rule is silently discarded during parsing.(CVE-2026-70463)\n\nrsync daemon 2.0.0 before 3.5.0 contains a denial of service vulnerability that allows unauthenticated remote attackers to exhaust daemon connection slots by stalling the handshake process before or after module selection without triggering the I/O timeout. Attackers can open many simultaneous connections and trickle data at the minimum rate to avoid timeout, or stall entirely before module selection where no timeout applies, consuming all available connection slots and denying service to legitimate clients.(CVE-2026-70464)","status":"published","published":"2026-09-20T13:23:31Z","modified":"2026-09-20T13:30:30.997420788Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:52:47.643553Z"},{"id":"OESA-2026-4072","title":"rsync security update","description":"Rsync is an open source utility that provides fast incremental file transfer. It uses the \u0026amp;quot;rsync algorithm\u0026amp;quot; which provides a very fast method for bringing remote files into sync. It does this by sending just the differences in the files across the link, without requiring that both sets of files are present at one of the ends of the link beforehand.\r\n\r\nSecurity Fix(es):\n\nRsync version 3.4.2 and prior contain symlink race condition vulnerabilities in path-based system calls including chmod, lchown, utimes, rename, unlink, mkdir, symlink, mknod, link, rmdir, and lstat that allow local attackers to redirect operations to files outside the exported rsync module. Attackers with local filesystem access can exploit the timing window between path resolution and syscall execution by swapping symlinks to apply sender-supplied permissions, ownership, timestamps, or filenames to arbitrary files outside the intended module boundary on rsync daemons configured with \u0026apos;use chroot = no\u0026apos;.(CVE-2026-43619)\n\nrsync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the rrsync restricted shell wrapper that allows authenticated clients to escape enforced directory restrictions by substituting a symlink for a path component after validation but before transfer processing. Attackers can additionally leverage unrestricted flags such as --copy-unsafe-links, -D, and --log-file through rrsync to read or write files outside the permitted directory subtree.(CVE-2026-53783)\n\nrsync before 3.5.0 contains a path traversal vulnerability that allows remote clients to access files outside the intended module root when use chroot is disabled and the module root path or a component of it is a symlink. The daemon calls chdir() to the module root at session initialization without resolving symlinks via realpath() or equivalent, causing subsequent relative-path operations to reference files relative to the symlink target rather than the intended module root, enabling unauthorized file access.(CVE-2026-53784)\n\nrsync before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to write files outside the intended destination directory tree by crafting relative paths with symlink components in --relative mode. The make_path() function follows symlinks pointing outside the destination tree while creating intermediate directories without verifying that created paths remain within the destination boundary, enabling arbitrary file writes on the receiver\u0026apos;s filesystem.(CVE-2026-53785)\n\nrsync before 3.5.0 contains a filter rule bypass vulnerability that allows authenticated clients to override module-level filter restrictions by supplying malicious --filter merge file directives. Attackers can inject client-side merge file directives during filter evaluation to introduce rules that supersede daemon module-level restrictions, gaining access to files the module filter was intended to exclude.(CVE-2026-53786)\n\nrsync before 3.5.0 contains a newline injection vulnerability in the name-converter uid/gid mapping interface that allows local attackers to forge protocol messages by creating user or group names containing newline characters. Attackers can inject malicious newline characters into names communicated over the pipe-based line-oriented protocol to cause the rsync daemon to process attacker-influenced data as legitimate protocol input, corrupting uid/gid mapping logic.(CVE-2026-53788)\n\nrsync before 3.5.0 contains an improper path handling vulnerability that allows a malicious sender to expand the scope of --delete operations beyond the intended destination subtree by sending a crafted file list that causes rsync to reclassify implied parent directory entries or treat synthetic paths as the transfer root. Attackers can exploit multiple variants including implied parent reclassification, synthetic root path construction, legacy protocol behavior below version 30, and non-directory root handling to cause the receiver to delete files outside the authorized destination directory.(CVE-2026-53789)\n\nrsync before 3.5.0 contains multiple command and argument injection vulnerabilities that allow attackers to execute arbitrary commands by supplying malicious input through several code paths, including the RSYNC_CONNECT_PROG environment variable, daemon hooks, the rsync-ssl wrapper, and remote-shell command newline injection. Attackers can inject shell metacharacters or newline characters into unsanitized user-supplied values such as hostnames and hostspecs to execute arbitrary commands under the privileges of the rsync process or the invoking user.(CVE-2026-53790)\n\nrsync daemon before 3.5.0 contains an IP address spoofing vulnerability that allows unauthenticated remote attackers to bypass IP-based access controls by sending a crafted PROXY protocol header with a forged source address. Attackers who can connect directly to the rsync daemon can inject a spoofed source IP in the PROXY protocol header to circumvent hosts allow/deny rules, gaining unauthorized access that would otherwise be blocked based on their real source address.(CVE-2026-53791)\n\nrsync before 3.5.0 contains an out-of-bounds read vulnerability in the sender-side block matching logic that allows a malicious receiver to trigger memory access before the start of an allocated buffer by sending a crafted checksum block with a length of zero. Attackers can send a specially crafted checksum set containing a zero-length block to cause a negative offset calculation during delta computation, resulting in an out-of-bounds read of file data buffer memory on the sender side.(CVE-2026-53792)\n\nrsync before 3.5.0 contains a path confinement bypass vulnerability that allows remote clients to escape the intended inner-module root confinement by constructing paths that resolve outside the chroot boundary when the module root contains a /./ boundary marker. Attackers can exploit improper handling of the /./ notation or forge delta-basis transfers referencing xname paths that cross the /./ boundary to gain unauthorized read or write access to files outside the module\u0026apos;s subtree.(CVE-2026-53793)\n\nrsync before 3.5.0 contains a logic error in --max-alloc handling that allows a sender or configuration setting --max-alloc=0 to disable allocation sanity checks entirely rather than enforcing a zero-byte cap. Attackers can exploit this flaw to cause the receiver to attempt unbounded memory allocations for file list and data structures, potentially exhausting available memory and causing a denial of service.(CVE-2026-53794)\n\nrsync before 3.5.0 contains an arbitrary file write vulnerability that allows attackers to write files outside the intended destination tree by specifying an absolute path via --temp-dir or --link-dest options. The rename-confinement logic is bypassed when these options resolve to paths outside the destination tree, enabling attacker-controlled values to write files to arbitrary locations accessible to the rsync process.(CVE-2026-53795)\n\nrsync before 3.5.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the non-daemon receiver\u0026apos;s destination directory handling that allows an attacker who can manipulate destination path parent components to redirect file writes to unintended locations. Attackers can substitute a symlink for a component of the destination path between the path resolution and chdir() call, causing the receiver\u0026apos;s working directory to be established outside the intended destination tree so that subsequent relative-path file writes land in unintended filesystem locations.(CVE-2026-53796)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability in the sender\u0026apos;s source tree traversal that allows an attacker who can manipulate a parent directory of the source tree to redirect file reads to unintended paths. Attackers can atomically replace a parent directory component with a symlink pointing outside the source root between path resolution and file open operations to disclose file contents outside the intended transfer root.(CVE-2026-53797)\n\nrsync before 3.5.0 contains a privilege confusion vulnerability in the name-converter subprocess uid/gid mapping that allows local attackers to cause transferred files to be owned by root by influencing name-converter responses to return empty values. When the name-converter subprocess returns an empty response for a uid or gid lookup, rsync incorrectly interprets it as a successful resolution to uid/gid 0 (root) rather than a lookup failure, and if the name-converter also signals fake super-user status, rsync proceeds with root ownership assignments for transferred files.(CVE-2026-53798)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability that allows local attackers to cause rsync to apply arbitrary ACLs or extended attributes to unintended files by substituting a symlink at a predictable destination path between the file write and the subsequent acl_set_file() or lsetxattr() call. Attackers can exploit this timing window to redirect ACL and xattr application through a crafted symlink to files outside the intended destination tree, potentially granting elevated permissions and enabling local privilege escalation.(CVE-2026-53799)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability in the --remove-source-files feature that allows attackers with symlink creation access to cause arbitrary file deletion. Attackers can atomically substitute a symlink for a source file between transfer completion and the unlink() call, causing rsync to delete the symlink target rather than the intended source file.(CVE-2026-53800)\n\nrsync before 3.5.0 contains a symlink race condition vulnerability in the sender\u0026apos;s directory scanning logic that allows attackers to cause the sender to enumerate and transfer files outside the module root\u0026apos;s intended subtree. Attackers who can create or manipulate symlinks in a path component of the scanned tree can replace a symlink with a directory entry pointing outside the module root between the lstat() call and the subsequent opendir() call, exposing files beyond the intended root in both daemon-mode and non-daemon sender-side scanning.(CVE-2026-53801)\n\nrsync before 3.5.0 contains an arbitrary file read vulnerability that allows attackers to read files accessible to the rsync daemon process by exploiting symlink following in input configuration file handling including --files-from, --password-file, and filter merge files. Attackers can place a symlink at a predictable --files-from or --password-file path, or supply a --files-from path that escapes the daemon module root, to read arbitrary files accessible to the rsync process.(CVE-2026-53802)\n\nrsync before 3.5.0 contains a symlink following vulnerability that allows local attackers to overwrite arbitrary files by placing a symlink at a predictable output path such as --log-file, --write-batch, or daemon-mode log and statistics paths. Attackers can exploit rsync\u0026apos;s failure to reject symlinks during ancillary file writes to redirect output to arbitrary filesystem locations, achieving local privilege escalation on installations where rsync runs with elevated privileges such as setuid or privileged daemon configurations.(CVE-2026-53803)\n\nrsync 3.1.0 before 3.5.0 contains an access control bypass vulnerability that allows remote attackers to circumvent hosts deny rules by inducing DNS resolution failures during hostname-based access control evaluation. When a DNS lookup for a hostname-based deny rule fails, the daemon skips the rule rather than defaulting to a deny decision, enabling attackers who can trigger DNS failures to bypass module-level IP access controls and gain unauthorized access to restricted module file trees.(CVE-2026-70452)\n\nrsync before 3.5.0 contains an algorithmic complexity vulnerability in the hash_search() function that allows a remote attacker to cause a denial of service by delivering a carefully constructed file list. A sender can exploit the quadratic-time worst-case behavior in hash lookups to exhaust receiver CPU resources with a modest number of crafted entries, causing a sustained denial of service.(CVE-2026-70453)\n\nrsync 3.2.0 through 3.2.3 (openssl mode) and rsync-ssl through 3.4.4 (stunnel mode) contain a TLS certificate validation vulnerability that allows on-path attackers to intercept encrypted sessions by presenting self-signed or otherwise invalid certificates. Attackers can exploit the failure to validate server TLS certificates against a trusted CA or verify certificate hostname matching to decrypt or tamper with rsync session content without detection by the client.(CVE-2026-70454)\n\nrsync 3.0.1 before 3.5.0 contains an out-of-bounds write vulnerability in the read_args() function that allows a malicious sender to corrupt adjacent heap memory by sending a crafted argument list. When the argument count causes the argv allocation to be exactly full, the trailing NULL terminator is written one slot beyond the allocation boundary, corrupting adjacent heap memory.(CVE-2026-70456)\n\nrsync 3.2.3 before 3.5.0 contains an out-of-bounds write in parse_size_arg() where the return value of snprintf() is used directly as an index into a .bss-segment array without bounds checking. When snprintf truncates the formatted size string, the return value equals the number of characters that would have been written including the truncated portion, and this value may exceed the array length. The subsequent indexed write targets memory outside the intended array bounds, corrupting .bss memory.(CVE-2026-70457)\n\nrsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.(CVE-2026-70458)\n\nrsync 3.0.0 before 3.5.0 contains a null pointer dereference vulnerability in the daemon child process that allows remote attackers to crash the daemon by sending a file list whose first entry is a dot entry not typed as a directory. The daemon dereferences the first file list entry as a directory structure pointer without verifying the entry type, resulting in an invalid or uninitialized pointer dereference that terminates the client connection.(CVE-2026-70459)\n\nrsync 2.3.3 before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to escape the module root by exploiting symlinks within the module file tree when using --partial-dir or --backup-dir options. Attackers with write access to place a symlink under the module root, or who can exploit a pre-existing trusted symlink, can direct file writes to locations outside the intended module root, achieving arbitrary file write relative to the module root parent.(CVE-2026-70460)\n\nrsync 3.2.5 before 3.5.0 contains a heap out-of-bounds write vulnerability that allows remote unauthenticated attackers to write one attacker-controlled byte past the end of a heap allocation by supplying a crafted files-from entry. Attackers can trigger the vulnerability against a read-only rsync daemon module by providing a files-from entry containing both an interior and trailing backslash, causing the add_implied_include() function to under-count the trailing backslash when sizing the destination buffer.(CVE-2026-70461)\n\nrsync 3.1.0 before 3.5.0 contains a signed integer overflow vulnerability in the I/O timeout implementation that allows attackers to permanently disable connection timeouts by injecting MSG_IO_TIMEOUT messages carrying non-positive (zero or negative) values. Attackers can craft malicious MSG_IO_TIMEOUT messages that cause the timeout variable to wrap to a non-positive value, preventing the timeout check from firing and enabling idle or stalled connections to hold daemon slots indefinitely, leading to resource exhaustion.(CVE-2026-70462)\n\nrsync 3.1.0 before 3.5.0 contains an authorization bypass in auth users directive parsing. The auth users parser uses comma-only tokenization when splitting the user list, which fails to correctly handle entries of the form @Group Name where the group name contains a space. The space within the group name causes the parser to split the entry at the space boundary, discarding the deny rule associated with the group. An authenticated user whose username or group membership would be denied by an @Group Name auth users entry can connect to a restricted module because the deny rule is silently discarded during parsing.(CVE-2026-70463)\n\nrsync daemon 2.0.0 before 3.5.0 contains a denial of service vulnerability that allows unauthenticated remote attackers to exhaust daemon connection slots by stalling the handshake process before or after module selection without triggering the I/O timeout. Attackers can open many simultaneous connections and trickle data at the minimum rate to avoid timeout, or stall entirely before module selection where no timeout applies, consuming all available connection slots and denying service to legitimate clients.(CVE-2026-70464)","status":"published","published":"2026-09-25T01:28:04Z","modified":"2026-09-25T01:45:11.308468052Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:52:47.643553Z"},{"id":"RHSA-2026:67462","title":"Red Hat Security Advisory: rsync security, bug fix, and enhancement update","status":"published","published":"2026-09-15T10:17:14Z","modified":"2026-10-10T10:18:13Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:22.406388Z"},{"id":"RHSA-2026:67463","title":"Red Hat Security Advisory: rsync security, bug fix, and enhancement update","status":"published","published":"2026-09-15T10:17:15Z","modified":"2026-10-10T10:18:14Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:22.406388Z"},{"id":"RHSA-2026:74095","title":"Red Hat Security Advisory: rsync security, bug fix, and enhancement update","status":"published","published":"2026-10-01T10:21:20Z","modified":"2026-10-10T10:21:11Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:22.928316Z"},{"id":"RLSA-2026:67462","title":"Important: rsync security, bug fix, and enhancement update","description":"The rsync utility enables the users to copy and synchronize files locally or across a network. Synchronization with rsync is fast because rsync only sends the differences in files over the network instead of sending whole files. The rsync utility is also used as a mirroring tool.\n\nSecurity Fix(es):\n\n* rsync: rsync 2.3.3 \u003c 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink (CVE-2026-70460)\n\n* rsync: rsync: TLS Certificate Validation Bypass allows interception of encrypted sessions (CVE-2026-70454)\n\n* rsync: rsync: Arbitrary file deletion via malicious file list (CVE-2026-53789)\n\n* rsync: rsync \u003c 3.5.0 Command Injection via Multiple Code Paths (CVE-2026-53790)\n\n* rsync: rsync: Memory corruption via crafted file entries (CVE-2026-70458)\n\n* rsync: rsync: Denial of Service via handshake stall (CVE-2026-70464)\n\n* rsync: rsync: Local Privilege Escalation via Symlink Following (CVE-2026-53803)\n\n* rsync: rsync: Unauthorized File Access via Symlink Module Root (CVE-2026-53784)\n\n* rsync: rsync: Authorization bypass via `auth users` directive parsing (CVE-2026-70463)\n\n* rsync: rsync 3.1.0 \u003c 3.5.0 Access Control Bypass via DNS Resolution Failure (CVE-2026-70452)\n\n* rsync: rsync \u003c 3.5.0 Daemon IP Spoofing via PROXY Protocol Header (CVE-2026-53791)\n\n* rsync: rsync: Arbitrary file write via --temp-dir or --link-dest options (CVE-2026-53795)\n\n* rsync: rsync: Heap Out-of-Bounds Write via crafted argument list (CVE-2026-70456)\n\n* rsync: rsync \u003c 3.5.0 Path Confinement Bypass via /./ Boundary Marker in Chroot Mode (CVE-2026-53793)\n\n* rsync: rsync: Denial of Service via Algorithmic Complexity (CVE-2026-70453)\n\n* rsync: rsync: Memory corruption via out-of-bounds write in size parsing (CVE-2026-70457)\n\n* rsync: rsync: Information disclosure and denial of service via crafted files-from entry (CVE-2026-70461)\n\n* rsync: rsync: Arbitrary File Read via Symlink Following (CVE-2026-53802)\n\n* rsync: rsync: Arbitrary file write via path traversal in --relative mode (CVE-2026-53785)\n\n* rsync: rsync: Directory escape via TOCTOU race condition in rrsync (CVE-2026-53783)\n\nBug Fix(es) and Enhancement(s):\n\n* Rebase rsync to version 3.2.7 in Rocky Linux9 (JIRA:Rocky Linux-248835)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2026-09-15T18:05:37.908911Z","modified":"2026-09-15T18:30:36.361277004Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:26.449929Z"},{"id":"RLSA-2026:67463","title":"Important: rsync security, bug fix, and enhancement update","description":"The rsync utility enables the users to copy and synchronize files locally or across a network. Synchronization with rsync is fast because rsync only sends the differences in files over the network instead of sending whole files. The rsync utility is also used as a mirroring tool.\n\nSecurity Fix(es):\n\n* rsync: rsync 2.3.3 \u003c 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink (CVE-2026-70460)\n\n* rsync: rsync: TLS Certificate Validation Bypass allows interception of encrypted sessions (CVE-2026-70454)\n\n* rsync: rsync: Arbitrary file deletion via malicious file list (CVE-2026-53789)\n\n* rsync: rsync \u003c 3.5.0 Command Injection via Multiple Code Paths (CVE-2026-53790)\n\n* rsync: rsync: Memory corruption via crafted file entries (CVE-2026-70458)\n\n* rsync: rsync: Denial of Service via handshake stall (CVE-2026-70464)\n\n* rsync: rsync: Local Privilege Escalation via Symlink Following (CVE-2026-53803)\n\n* rsync: rsync: Unauthorized File Access via Symlink Module Root (CVE-2026-53784)\n\n* rsync: rsync: Authorization bypass via `auth users` directive parsing (CVE-2026-70463)\n\n* rsync: rsync 3.1.0 \u003c 3.5.0 Access Control Bypass via DNS Resolution Failure (CVE-2026-70452)\n\n* rsync: rsync \u003c 3.5.0 Daemon IP Spoofing via PROXY Protocol Header (CVE-2026-53791)\n\n* rsync: rsync: Arbitrary file write via --temp-dir or --link-dest options (CVE-2026-53795)\n\n* rsync: rsync: Heap Out-of-Bounds Write via crafted argument list (CVE-2026-70456)\n\n* rsync: rsync \u003c 3.5.0 Path Confinement Bypass via /./ Boundary Marker in Chroot Mode (CVE-2026-53793)\n\n* rsync: rsync: Denial of Service via Algorithmic Complexity (CVE-2026-70453)\n\n* rsync: rsync: Denial of Service via Zstandard compression thread exhaustion (CVE-2026-70455)\n\n* rsync: rsync: Memory corruption via out-of-bounds write in size parsing (CVE-2026-70457)\n\n* rsync: rsync: Information disclosure and denial of service via crafted files-from entry (CVE-2026-70461)\n\n* rsync: rsync: Arbitrary File Read via Symlink Following (CVE-2026-53802)\n\n* rsync: rsync: Arbitrary file write via path traversal in --relative mode (CVE-2026-53785)\n\n* rsync: rsync: Directory escape via TOCTOU race condition in rrsync (CVE-2026-53783)\n\nBug Fix(es) and Enhancement(s):\n\n* Rebase rsync to version 3.5.0 in Rocky Linux10 (JIRA:Rocky Linux-246094)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2026-09-15T12:08:56.876794Z","modified":"2026-09-15T12:30:03.321710965Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:26.449929Z"},{"id":"RLSA-2026:74095","title":"Important: rsync security, bug fix, and enhancement update","description":"The rsync utility enables the users to copy and synchronize files locally or across a network. Synchronization with rsync is fast because rsync only sends the differences in files over the network instead of sending whole files. The rsync utility is also used as a mirroring tool.\n\nSecurity Fix(es):\n\n* rsync: rsync 2.3.3 \u003c 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink (CVE-2026-70460)\n\n* rsync: rsync: Arbitrary file deletion via malicious file list (CVE-2026-53789)\n\n* rsync: rsync \u003c 3.5.0 Command Injection via Multiple Code Paths (CVE-2026-53790)\n\n* rsync: rsync: Memory corruption via crafted file entries (CVE-2026-70458)\n\n* rsync: rsync: Denial of Service via handshake stall (CVE-2026-70464)\n\n* rsync: rsync: Local Privilege Escalation via Symlink Following (CVE-2026-53803)\n\n* rsync: rsync: Unauthorized File Access via Symlink Module Root (CVE-2026-53784)\n\n* rsync: rsync: Authorization bypass via `auth users` directive parsing (CVE-2026-70463)\n\n* rsync: rsync 3.1.0 \u003c 3.5.0 Access Control Bypass via DNS Resolution Failure (CVE-2026-70452)\n\n* rsync: rsync: Arbitrary file write via --temp-dir or --link-dest options (CVE-2026-53795)\n\n* rsync: rsync: Heap Out-of-Bounds Write via crafted argument list (CVE-2026-70456)\n\n* rsync: rsync \u003c 3.5.0 Path Confinement Bypass via /./ Boundary Marker in Chroot Mode (CVE-2026-53793)\n\n* rsync: rsync: Denial of Service via Algorithmic Complexity (CVE-2026-70453)\n\n* rsync: rsync: Information disclosure and denial of service via crafted files-from entry (CVE-2026-70461)\n\n* rsync: rsync: Arbitrary File Read via Symlink Following (CVE-2026-53802)\n\n* rsync: rsync: Arbitrary file write via path traversal in --relative mode (CVE-2026-53785)\n\n* rsync: rsync: Directory escape via TOCTOU race condition in rrsync (CVE-2026-53783)\n\nBug Fix(es) and Enhancement(s):\n\n* Fix latest CVEs in rsync in Rocky Linux8 (JIRA:Rocky Linux-256903)\n\n* rsync-3.1.3-27.el8_10 regression: rsync daemon rejects legitimate cross-device symlinks with EXDEV when use chroot = no (JIRA:Rocky Linux-239553)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2026-10-01T18:00:58.911304Z","modified":"2026-10-01T18:24:43.245498218Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:26.449929Z"},{"id":"UBUNTU-CVE-2026-70458","description":"rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.","status":"published","published":"2026-08-13T15:19:00Z","modified":"2026-10-17T12:59:29.089374935Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"},{"version":"4.0","score":8.8,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","level":"high"}],"updated_at":"2026-11-02T16:56:57.159276Z"},{"id":"ALSA-2026:67462","title":"Important: rsync security, bug fix, and enhancement update","description":"The rsync utility enables the users to copy and synchronize files locally or across a network. Synchronization with rsync is fast because rsync only sends the differences in files over the network instead of sending whole files. The rsync utility is also used as a mirroring tool.  \n\nSecurity Fix(es):  \n\n  * rsync: rsync 2.3.3 \u003c 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink (CVE-2026-70460)\n  * rsync: rsync: TLS Certificate Validation Bypass allows interception of encrypted sessions (CVE-2026-70454)\n  * rsync: rsync: Arbitrary file deletion via malicious file list (CVE-2026-53789)\n  * rsync: rsync \u003c 3.5.0 Command Injection via Multiple Code Paths (CVE-2026-53790)\n  * rsync: rsync: Memory corruption via crafted file entries (CVE-2026-70458)\n  * rsync: rsync: Denial of Service via handshake stall (CVE-2026-70464)\n  * rsync: rsync: Local Privilege Escalation via Symlink Following (CVE-2026-53803)\n  * rsync: rsync: Unauthorized File Access via Symlink Module Root (CVE-2026-53784)\n  * rsync: rsync: Authorization bypass via `auth users` directive parsing (CVE-2026-70463)\n  * rsync: rsync 3.1.0 \u003c 3.5.0 Access Control Bypass via DNS Resolution Failure (CVE-2026-70452)\n  * rsync: rsync \u003c 3.5.0 Daemon IP Spoofing via PROXY Protocol Header (CVE-2026-53791)\n  * rsync: rsync: Arbitrary file write via --temp-dir or --link-dest options (CVE-2026-53795)\n  * rsync: rsync: Heap Out-of-Bounds Write via crafted argument list (CVE-2026-70456)\n  * rsync: rsync \u003c 3.5.0 Path Confinement Bypass via /./ Boundary Marker in Chroot Mode (CVE-2026-53793)\n  * rsync: rsync: Denial of Service via Algorithmic Complexity (CVE-2026-70453)\n  * rsync: rsync: Memory corruption via out-of-bounds write in size parsing (CVE-2026-70457)\n  * rsync: rsync: Information disclosure and denial of service via crafted files-from entry (CVE-2026-70461)\n  * rsync: rsync: Arbitrary File Read via Symlink Following (CVE-2026-53802)\n  * rsync: rsync: Arbitrary file write via path traversal in --relative mode (CVE-2026-53785)\n  * rsync: rsync: Directory escape via TOCTOU race condition in rrsync (CVE-2026-53783)\n\n\nBug Fix(es) and Enhancement(s):  \n\n  * Rebase rsync to version 3.2.7 in AlmaLinux9 (JIRA:AlmaLinux-248835)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n","status":"published","published":"2026-09-14T00:00:00Z","modified":"2026-10-29T11:32:32.109570707Z","updated_at":"2026-11-02T15:27:55.200553Z"},{"id":"ALSA-2026:67463","title":"Important: rsync security, bug fix, and enhancement update","description":"The rsync utility enables the users to copy and synchronize files locally or across a network. Synchronization with rsync is fast because rsync only sends the differences in files over the network instead of sending whole files. The rsync utility is also used as a mirroring tool.  \n\nSecurity Fix(es):  \n\n  * rsync: rsync 2.3.3 \u003c 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink (CVE-2026-70460)\n  * rsync: rsync: TLS Certificate Validation Bypass allows interception of encrypted sessions (CVE-2026-70454)\n  * rsync: rsync: Arbitrary file deletion via malicious file list (CVE-2026-53789)\n  * rsync: rsync \u003c 3.5.0 Command Injection via Multiple Code Paths (CVE-2026-53790)\n  * rsync: rsync: Memory corruption via crafted file entries (CVE-2026-70458)\n  * rsync: rsync: Denial of Service via handshake stall (CVE-2026-70464)\n  * rsync: rsync: Local Privilege Escalation via Symlink Following (CVE-2026-53803)\n  * rsync: rsync: Unauthorized File Access via Symlink Module Root (CVE-2026-53784)\n  * rsync: rsync: Authorization bypass via `auth users` directive parsing (CVE-2026-70463)\n  * rsync: rsync 3.1.0 \u003c 3.5.0 Access Control Bypass via DNS Resolution Failure (CVE-2026-70452)\n  * rsync: rsync \u003c 3.5.0 Daemon IP Spoofing via PROXY Protocol Header (CVE-2026-53791)\n  * rsync: rsync: Arbitrary file write via --temp-dir or --link-dest options (CVE-2026-53795)\n  * rsync: rsync: Heap Out-of-Bounds Write via crafted argument list (CVE-2026-70456)\n  * rsync: rsync \u003c 3.5.0 Path Confinement Bypass via /./ Boundary Marker in Chroot Mode (CVE-2026-53793)\n  * rsync: rsync: Denial of Service via Algorithmic Complexity (CVE-2026-70453)\n  * rsync: rsync: Denial of Service via Zstandard compression thread exhaustion (CVE-2026-70455)\n  * rsync: rsync: Memory corruption via out-of-bounds write in size parsing (CVE-2026-70457)\n  * rsync: rsync: Information disclosure and denial of service via crafted files-from entry (CVE-2026-70461)\n  * rsync: rsync: Arbitrary File Read via Symlink Following (CVE-2026-53802)\n  * rsync: rsync: Arbitrary file write via path traversal in --relative mode (CVE-2026-53785)\n  * rsync: rsync: Directory escape via TOCTOU race condition in rrsync (CVE-2026-53783)\n\n\nBug Fix(es) and Enhancement(s):  \n\n  * Rebase rsync to version 3.5.0 in AlmaLinux10 (JIRA:AlmaLinux-246094)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n","status":"published","published":"2026-09-14T00:00:00Z","modified":"2026-10-29T11:30:43.480628079Z","updated_at":"2026-11-02T15:27:55.200553Z"},{"id":"ALSA-2026:74095","title":"Important: rsync security, bug fix, and enhancement update","description":"The rsync utility enables the users to copy and synchronize files locally or across a network. Synchronization with rsync is fast because rsync only sends the differences in files over the network instead of sending whole files. The rsync utility is also used as a mirroring tool.  \n\nSecurity Fix(es):  \n\n  * rsync: rsync 2.3.3 \u003c 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink (CVE-2026-70460)\n  * rsync: rsync: Arbitrary file deletion via malicious file list (CVE-2026-53789)\n  * rsync: rsync \u003c 3.5.0 Command Injection via Multiple Code Paths (CVE-2026-53790)\n  * rsync: rsync: Memory corruption via crafted file entries (CVE-2026-70458)\n  * rsync: rsync: Denial of Service via handshake stall (CVE-2026-70464)\n  * rsync: rsync: Local Privilege Escalation via Symlink Following (CVE-2026-53803)\n  * rsync: rsync: Unauthorized File Access via Symlink Module Root (CVE-2026-53784)\n  * rsync: rsync: Authorization bypass via `auth users` directive parsing (CVE-2026-70463)\n  * rsync: rsync 3.1.0 \u003c 3.5.0 Access Control Bypass via DNS Resolution Failure (CVE-2026-70452)\n  * rsync: rsync: Arbitrary file write via --temp-dir or --link-dest options (CVE-2026-53795)\n  * rsync: rsync: Heap Out-of-Bounds Write via crafted argument list (CVE-2026-70456)\n  * rsync: rsync \u003c 3.5.0 Path Confinement Bypass via /./ Boundary Marker in Chroot Mode (CVE-2026-53793)\n  * rsync: rsync: Denial of Service via Algorithmic Complexity (CVE-2026-70453)\n  * rsync: rsync: Information disclosure and denial of service via crafted files-from entry (CVE-2026-70461)\n  * rsync: rsync: Arbitrary File Read via Symlink Following (CVE-2026-53802)\n  * rsync: rsync: Arbitrary file write via path traversal in --relative mode (CVE-2026-53785)\n  * rsync: rsync: Directory escape via TOCTOU race condition in rrsync (CVE-2026-53783)\n\n\nBug Fix(es) and Enhancement(s):  \n\n  * Fix latest CVEs in rsync in AlmaLinux8 (JIRA:AlmaLinux-256903)\n  * rsync-3.1.3-27.el8_10 regression: rsync daemon rejects legitimate cross-device symlinks with EXDEV when use chroot = no (JIRA:AlmaLinux-239553)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n","status":"published","published":"2026-09-30T00:00:00Z","modified":"2026-10-29T11:02:29.750306755Z","updated_at":"2026-11-02T15:27:55.200553Z"},{"id":"AZL-95759","title":"CVE-2026-70458 affecting package rsync for versions less than 3.5.0-1","description":"rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.","status":"published","published":"2026-08-13T15:19:59Z","modified":"2026-09-10T14:16:59.49021244Z","updated_at":"2026-11-02T15:28:12.028669Z"},{"id":"CLSA-2026-1788335736","title":"Fix of 13 CVEs","description":"   * SECURITY UPDATE: peer-driven one-byte heap out-of-bounds write in\n     add_implied_include() from a files-from entry carrying both an interior\n     and a trailing backslash:\n     - debian/patches/els/0009-CVE-2026-70461.patch: count a trailing\n       backslash when sizing the appended-wildcard pattern.\n     - CVE-2026-70461.\n   * SECURITY UPDATE: heap out-of-bounds write in read_args() when the peer's\n     argument count lands exactly on the argv allocation:\n     - debian/patches/els/0010-CVE-2026-70456.patch: reserve room for the\n       trailing NULL terminator.\n     - CVE-2026-70456.\n   * SECURITY UPDATE: out-of-bounds write from a file entry marked\n     FLAG_HLINKED that the receiver accepted with hard-link preservation\n     inactive:\n     - debian/patches/els/0011-CVE-2026-70458.patch: gate FLAG_HLINKED on\n       preserve_hard_links and exclude directories.\n     - CVE-2026-70458.\n   * SECURITY UPDATE: sender-side out-of-bounds read driven by a malicious\n     receiver's checksum header with a non-zero block count and a zero block\n     length:\n     - debian/patches/els/0012-CVE-2026-53792.patch: reject a zero block\n       length in read_sum_head().\n     - CVE-2026-53792.\n   * SECURITY UPDATE: CPU exhaustion in the sending process via\n     quadratic-time behaviour in hash_search(), driven by a malicious\n     receiver's crafted equal-weak-checksum block list. The attacker is the\n     receiver, but the cycles burned are the sender's: hash_search() is\n     reached only through match_sums(), whose sole caller is send_files() in\n     sender.c. NVD's text attributes the CPU to the receiver; the direction\n     stated here is what the code does:\n     - debian/patches/els/0013-CVE-2026-70453.patch: bound the per-offset\n       chain walk.\n     - CVE-2026-70453.\n   * SECURITY UPDATE: daemon \"hosts deny\" failing open when a configured\n     hostname token cannot be resolved:\n     - debian/patches/els/0014-CVE-2026-70452.patch: treat an unresolvable\n       deny-list token as a match.\n     - CVE-2026-70452.\n   * SECURITY UPDATE: daemon \"auth users\" ignoring its documented comma-only\n     parsing, silently discarding a deny rule that names a group whose name\n     contains a space:\n     - debian/patches/els/0015-CVE-2026-70463.patch: parse the list with\n       conf_strtok().\n     - CVE-2026-70463.\n   * SECURITY UPDATE: peer-supplied MSG_IO_TIMEOUT disabling the client's own\n     I/O timeout through a non-positive or overflowing value:\n     - debian/patches/els/0016-CVE-2026-70462.patch: cap the received value\n       and make set_io_timeout() arithmetic overflow-safe.\n     - CVE-2026-70462.\n   * SECURITY UPDATE: client-supplied --filter merge file bypassing the daemon\n     module filter list:\n     - debian/patches/els/0017-CVE-2026-53786.patch: strip the module-dir\n       prefix before the daemon-filter check.\n     - CVE-2026-53786.\n   * SECURITY UPDATE: per-connection daemon child crash on a crafted first\n     incremental file list whose transfer root is a non-directory dot entry:\n     - debian/patches/els/0018-CVE-2026-70459.patch: reject a non-directory\n       transfer-root entry and require a dir_flist entry before trusting\n       parent_ndx 0.\n     - CVE-2026-70459.\n   * SECURITY UPDATE: malicious sender widening the receiver's --delete scope\n     beyond the destination subtree via implied-parent reclassification:\n     - debian/patches/els/0019-CVE-2026-53789.patch: force implied-parent\n       directories non-content on the receiver, including the synthetic\n       transfer root and the pre-protocol-30 encoding.\n     - CVE-2026-53789.\n   * SECURITY UPDATE: unauthenticated pre-transfer handshake stall holding a\n     per-connection daemon child past the module's max connections limit:\n     - debian/patches/els/0020-CVE-2026-70464.patch: bound every\n       peer-controlled handshake read with an absolute deadline and cap the\n       early-protocol argument count.\n     - CVE-2026-70464.\n   * SECURITY UPDATE: command and argument injection through the\n     RSYNC_CONNECT_PROG %H host substitution, through unquoted arguments in a\n     --write-batch replay script, and through remote-shell argument quoting\n     that did not escape the newline, the carriage return or the backtick:\n     - debian/patches/els/0021-CVE-2026-53790.patch: shell-quote and validate\n       the connect host, and quote every replay-script argument.\n     - debian/patches/els/0025-CVE-2026-53790-safe-arg-shell-chars.patch: add\n       the newline, the carriage return and the backtick to safe_arg()'s\n       SHELL_CHARS escape set. safe_arg() escapes metacharacters because the\n       remote end is reached as \"ssh \u003chost\u003e rsync --server ...\", where ssh\n       joins the command words and the remote sshd hands the string to the\n       remote user's login shell, which re-parses it; an unescaped newline\n       therefore ended the transfer command and ran what followed, and an\n       unescaped backtick opened a command substitution. This package\n       acquired safe_arg() from els/0001-CVE-2022-29154.patch, whose donor\n       predates the backtick's addition upstream.\n     - Partial fix: the daemon %RSYNC_*% exec-hook expansions do not exist in\n       3.1.3 and rsync-ssl is not installed by debian/rules, so those two of\n       the four sinks named in the advisory are not present in this package.\n     - CVE-2026-53790.\n   * SECURITY UPDATE: further out-of-bounds F_SUM() reads where the checksum\n     extra slot was never reserved -- a daemon sender with \"%C\" in its log\n     format, a hard-linked non-regular entry compared against a basis dir,\n     and \"%C\" on a deletion:\n     - debian/patches/els/0022-CVE-2026-70458.patch: set\n       sender_keeps_checksum in start_server(), require S_ISREG(file-\u003emode)\n       before the content compare in hard_link_check(), and skip the\n       checksum for an ITEM_DELETED entry.\n     - CVE-2026-70458.\n   * Drop two peer-reachable assert() aborts (no CVE assigned; carried from\n     the same upstream commit as several of the fixes above, and live in the\n     shipped binary because nothing in the build defines NDEBUG):\n     - debian/patches/els/0023-peer-reachable-asserts.patch: turn an\n       undeclared cross-flist hard-link gnum into a protocol error instead of\n       an assert, and stop asserting !is_utf8 when a daemon receiver\n       forwards a peer message to the generator.\n   * Bound merge-file include recursion (no CVE assigned; the remaining\n     peer-reachable crash hunk of the same upstream commit several of the\n     fixes above come from). A merge file's content may name another merge\n     file, so parse_filter_file() re-enters itself with a BIGPATHBUFLEN\n     stack buffer per level; a self-referencing per-directory merge file,\n     whose content the peer supplies through the transferred tree, recursed\n     until the stack was exhausted (SIGSEGV):\n     - debian/patches/els/0024-merge-file-depth-cap.patch: add\n       MAX_MERGE_DEPTH and a nesting counter.\n   * Add committed regression tests to the shipped test suite for the six\n     fixes that a black-box test can observe, each carried by the patch it\n     proves and each failing without that patch:\n     - testsuite/cve-2026-70452.test (els/0014), an unresolvable \"hosts deny\"\n       token must deny.\n     - testsuite/cve-2026-70463.test (els/0015), the first word of a\n       space-bearing \"auth users\" entry must not become an allow rule.\n     - testsuite/cve-2026-53786.test (els/0017), a daemon filter rule must\n       govern a client merge file, and an \"exclude from\" path that only shares\n       the module path's textual prefix must not be truncated.\n     - testsuite/cve-2026-53790.test (els/0021), a newline-bearing filter rule\n       must not reach the replay script and an injected RSYNC_CONNECT_PROG %H\n       host must not execute.\n     - testsuite/cve-2026-53790-shell-chars.test (els/0025), a newline, a\n       carriage return or a backtick in a path must not execute a command on\n       the remote shell, and an ordinary transfer over the same remote shell\n       must still work.\n     - testsuite/cve-2026-70458.test (els/0022), the daemon's logged \"%C\" must\n       be the file's checksum, not adjacent pool memory.\n     - testsuite/merge-depth.test (els/0024), a self-referencing merge file\n       must be refused, not crash the process.\n     - testsuite/cve-2026-53790-safe-arg-uninit.test (els/0027), a trailing\n       backslash in a path must reach the remote shell doubled, and no stray\n       byte may follow a path that carries a backslash.\n   * SECURITY UPDATE: safe_arg() sized its result one byte larger than it\n     wrote for every backslash that precedes a wildcard and for a trailing\n     backslash, so the closing NUL landed past the last byte written and\n     uninitialised heap was returned inside the string handed to the remote\n     shell (--protect-args is off by default in 3.1.3). The same defect left a\n     trailing backslash unescaped there, where it escapes the following space\n     and joins the next word:\n     - debian/patches/els/0027-CVE-2026-53790-safe-arg-uninit.patch: make the\n       escape counter mirror the writer and guard the WILD_CHARS lookup with\n       f[1]. Upstream's own stable-branch backport (1aef79e1 on\n       v3.2.7-sec-patches3, from 22efd249), applied unchanged.\n     - CVE-2026-53790.\n   * SECURITY UPDATE: a fourth out-of-bounds F_SUM() read, specific to this\n     package. generator.c unchanged_file() guards the checksum compare on the\n     destination's on-disk mode while the slot is reserved from the\n     peer-supplied file-\u003emode; Debian's copy-devices.diff lets a device entry\n     reach it, so with -c --copy-devices a sender's device entry whose\n     destination is an existing regular file reads below its pool slot:\n     - debian/patches/els/0030-CVE-2026-70458-copy-devices.patch: require\n       S_ISREG(file-\u003emode) as well.\n     - CVE-2026-70458.\n   * Carry the four remaining hunks of upstream 3eeedf8d that land in\n     functions this series already patches (no CVE assigned; the same\n     malicious-peer hardening commit seven of the patches above cite):\n     - debian/patches/els/0026-donor-parity-3eeedf8d.patch: re-check the block\n       length before adopting want_i in hash_search(), clamp a peer-supplied\n       s-\u003eflength to the local length in match_sums(), and refuse a sub-flist\n       that arrives after the final flist was freed or that names a cleared\n       dir_flist slot in recv_file_list().\n   * Fix secure_relative_open() never returning a directory descriptor. The\n     per-component walk only assigned the result in its ENOTDIR arm, so a\n     path that resolved to a directory fell through to \"errno = EINVAL\" and\n     returned -1. Every permission change on a daemon receiver running with\n     \"use chroot = no\" therefore failed with \"failed to set permissions ...\n     Invalid argument (22)\" and the transfer exited 23. Introduced by\n     els/0006-CVE-2026-29518.patch, which added both the helper and its\n     O_DIRECTORY callers:\n     - debian/patches/els/0029-secure-relative-open-dirfd.patch.\n   * Run the upstream testsuite during the build, so the regression tests\n     above are load-bearing:\n     - debian/patches/els/0028-testsuite-harness.patch: add the missing\n       syscall.o stubs (noatime, am_daemon, am_chrooted) to tls.c,\n       trimslash.c and t_unsafe.c, without which \"make check\" could not even\n       link its helper programs, and let runtests.sh honour a $skiptests list.\n     - debian/rules: run \"make check\" from build-stamp unless\n       DEB_BUILD_OPTIONS=nocheck, excluding devices and devices-fake, which\n       fail identically on 3.1.3 with only the Debian patches applied.","status":"published","published":"2026-09-02T07:58:24Z","modified":"2026-10-26T09:43:29.311029583Z","updated_at":"2026-11-02T15:43:47.591214Z"},{"id":"CLSA-2026-1789662743","title":"Fix of 6 CVEs","description":"   * SECURITY UPDATE: shell metacharacter injection via daemon config hooks and RSYNC_CONNECT_PROG\n     - debian/patches/CVE-2026-53790.patch: backport the upstream fix\n     - CVE-2026-53790\n   * SECURITY UPDATE: daemon inner-chroot module path escape in the /./ handling\n     - debian/patches/CVE-2026-53793.patch: backport the upstream fix\n     - CVE-2026-53793\n   * SECURITY UPDATE: unbounded hash chain walk in hash_search()\n     - debian/patches/CVE-2026-70453.patch: backport the upstream fix\n     - CVE-2026-70453\n   * SECURITY UPDATE: out-of-bounds F_SUM read in hard_link_check()\n     - debian/patches/CVE-2026-70458.patch: backport the upstream fix\n     - CVE-2026-70458\n   * SECURITY UPDATE: I/O timeout bypass via MSG_IO_TIMEOUT\n     - debian/patches/CVE-2026-70462.patch: backport the upstream fix\n     - CVE-2026-70462\n   * SECURITY UPDATE: unbounded pre-transfer handshake in start_daemon()\n     - debian/patches/CVE-2026-70464.patch: backport the upstream fix\n     - CVE-2026-70464","status":"published","published":"2026-09-17T16:32:38Z","modified":"2026-10-26T09:32:02.125532613Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CLSA-2026-1789730480","title":"rsync: Fix of 6 CVEs","description":"- CVE-2026-53793: confine the alt-dest basis stat in try_dests and hard_link_check\n- CVE-2026-70458: skip the F_SUM read for ITEM_DELETED in log_formatted","status":"published","published":"2026-09-18T11:21:34Z","modified":"2026-10-26T09:31:59.235026315Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CLSA-2026-1789735848","title":"Fix of 6 CVEs","description":"   * SECURITY UPDATE: unbounded hash-chain walk in the delta-transfer matcher\n     - debian/patches/CVE-2026-70453.patch: bound the hash_search() chain walk\n       in match.c so a crafted checksum set cannot drive quadratic CPU use\n     - CVE-2026-70453\n   * SECURITY UPDATE: peer-supplied I/O timeout accepted as non-positive\n     - debian/patches/CVE-2026-70462.patch: reject a non-positive\n       MSG_IO_TIMEOUT from the peer in io.c\n     - CVE-2026-70462\n   * SECURITY UPDATE: unbounded daemon pre-transfer handshake\n     - debian/patches/CVE-2026-70464.patch: bound the pre-transfer handshake\n       with a timeout in clientserver.c and io.c\n     - CVE-2026-70464\n   * SECURITY UPDATE: malicious-peer protocol input and checksum-slot lifetime\n     - debian/patches/CVE-2026-70458-1.patch: daemon robustness against\n       malicious-peer protocol input\n     - debian/patches/CVE-2026-70458-2.patch: guard the F_SUM checksum-slot\n       lifetime in hlink.c and main.c\n     - debian/patches/CVE-2026-70458-3-copy-devices.patch: extend the same\n       guard to the copy-devices path\n     - CVE-2026-70458\n   * SECURITY UPDATE: daemon authentication, access and argument hardening\n     - debian/patches/CVE-2026-53790-1.patch: harden daemon authentication,\n       access, socket and argument handling\n     - debian/patches/CVE-2026-53790-2-shell-chars.patch: confine operator- and\n       peer-supplied paths to the served tree and reject shell metacharacters\n     - debian/patches/CVE-2026-53790-3-uninit.patch: fix a safe_arg()\n       uninitialized-byte leak in options.c\n     - CVE-2026-53790\n   * SECURITY UPDATE: inner-module escape for a daemon module using /./\n     - debian/patches/CVE-2026-53793-1-basis-paths.patch: stat alternate-basis\n       candidates through the confined resolver in generator.c\n     - debian/patches/CVE-2026-53793-2-inner-module.patch: widen the\n       use_secure_symlinks and change_dir() gates from \"am_daemon \u0026\u0026\n       !am_chrooted\" to \"am_daemon \u0026\u0026 (!am_chrooted || module_dirlen)\" so an\n       inner module root is the trust boundary, not the kernel chroot\n     - CVE-2026-53793","status":"published","published":"2026-09-18T12:51:03Z","modified":"2026-10-26T09:43:52.540591913Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CLSA-2026-1789737420","title":"rsync: Fix of 6 CVEs","description":"- CVE-2026-53793: confine the alt-dest basis stat in try_dests and hard_link_check\n- CVE-2026-70458: skip the F_SUM read for ITEM_DELETED in log_formatted","status":"published","published":"2026-09-18T13:17:20Z","modified":"2026-10-26T09:31:56.207879124Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CLSA-2026-1789737518","title":"rsync: Fix of 8 CVEs","description":"- CVE-2026-70461: count a trailing backslash when sizing the implied-include\n  filter rule, so a --files-from entry ending in a backslash can no longer\n  write one attacker-controlled byte past the rule's heap allocation\n- CVE-2026-70456: reserve the slot read_args() needs for its trailing NULL, so\n  a peer argument count landing exactly on maxargs cannot write one pointer\n  past the argv allocation\n- CVE-2026-70458: refuse FLAG_HLINKED when hard links are not in use and on a\n  directory entry, so a peer cannot displace the checksum slot through\n  hard-link extras that were never reserved; gate the hard-link basis check on\n  S_ISREG(file-\u003emode) so a hard-linked symlink or device cannot read a checksum\n  slot it never had; also set sender_keeps_checksum in the daemon-as-sender\n  path so %C cannot log adjacent heap\n- CVE-2026-70462: reject a non-positive MSG_IO_TIMEOUT from the peer and cap it\n  at 24 hours, and make set_io_timeout()'s arithmetic overflow-safe, so a\n  crafted server can neither disable the client's --timeout nor spin it at 100%\n  CPU on a negative select() timeout\n- CVE-2026-70453: bound the hash_search() chain walk at MAX_CHAIN_LEN, so a\n  basis file whose weak checksums all collide cannot drive an\n  O(file_size * chain_length) scan\n- CVE-2026-53785: create each implied parent directory through do_mkdir_at()\n  against a held O_NOFOLLOW directory fd, so a parent component raced into a\n  symlink can no longer place --relative directories outside the destination\n- CVE-2026-53794: reject --max-alloc=0, which disabled the per-allocation size\n  cap entirely instead of enforcing a zero one\n- CVE-2026-53790: shell-escape %VAR% expansions for their quoting context in\n  the daemon's exec hooks and refuse a peer value holding shell syntax, quote\n  the program names the rsync-ssl helper execs, and widen the remote-shell\n  safe_arg() escape set","status":"published","published":"2026-09-18T13:18:55Z","modified":"2026-10-26T09:43:29.663654981Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CLSA-2026-1789749013","title":"rsync: Fix of 6 CVEs","description":"- CVE-2026-53793: confine the alt-dest basis stat in try_dests and hard_link_check\n- CVE-2026-70458: skip the F_SUM read for ITEM_DELETED in log_formatted","status":"published","published":"2026-09-21T03:06:32Z","modified":"2026-10-26T09:31:48.764604054Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CLSA-2026-1789783256","title":"rsync: Fix of 7 CVEs","description":"- CVE-2026-70456: reserve the slot read_args() needs for its trailing NULL, so\n  a peer argument count landing exactly on maxargs cannot write one pointer\n  past the argv allocation\n- CVE-2026-70458: refuse FLAG_HLINKED when hard links are not in use and on a\n  directory entry, so a peer cannot displace the checksum slot through\n  hard-link extras that were never reserved; also set sender_keeps_checksum in\n  the daemon-as-sender path, and skip the content-based basis match for a\n  hard-linked non-regular file, so %C and --compare-dest cannot read a\n  checksum slot that was never allocated\n- CVE-2026-70462: reject a non-positive MSG_IO_TIMEOUT from the peer and cap it\n  at 24 hours, and make set_io_timeout()'s arithmetic overflow-safe, so a\n  crafted server can neither disable the client's --timeout nor spin it at 100%\n  CPU on a negative select() timeout\n- CVE-2026-70453: bound the hash_search() chain walk at MAX_CHAIN_LEN, so a\n  basis file whose weak checksums all collide cannot drive an\n  O(file_size * chain_length) scan\n- CVE-2026-53785: create each implied parent directory through do_mkdir_at()\n  against a held O_NOFOLLOW directory fd, and widen that wrapper's gate from\n  a non-chrooted daemon to any non-chrooted receiver as upstream does, so a\n  parent component raced into a symlink can no longer place --relative\n  directories outside the destination over ssh either\n- CVE-2026-53794: reject --max-alloc=0, which disabled the per-allocation size\n  cap entirely instead of enforcing a zero one\n- CVE-2026-53790: shell-escape %VAR% expansions for their quoting context in\n  the daemon's exec hooks and refuse a peer value holding shell syntax, quote\n  the program names the rsync-ssl helper execs and restrict the hostname it\n  interpolates into them, refuse a shell-active RSYNC_CONNECT_PROG host, and\n  widen the remote-shell safe_arg() escape set","status":"published","published":"2026-09-19T02:01:14Z","modified":"2026-10-26T09:43:41.062984326Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CLSA-2026-1790173668","title":"rsync: Fix of 6 CVEs","description":"- CVE-2026-53790: command injection in the daemon pre-/post-xfer exec hooks and RSYNC_CONNECT_PROG\n- CVE-2026-70453: denial of service in hash_search() -- unbounded chain walk\n- CVE-2026-70456: out-of-bounds write in read_args() -- no slot reserved for the trailing NULL\n- CVE-2026-70458: out-of-bounds read of the F_SUM slot in hard_link_check()\n- CVE-2026-70462: denial of service via a peer-supplied MSG_IO_TIMEOUT in set_io_timeout()\n- CVE-2026-70464: denial of service -- unbounded daemon pre-transfer handshake","status":"published","published":"2026-09-23T14:28:08Z","modified":"2026-10-26T09:31:51.513484635Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CLSA-2026-1790267010","title":"rsync: Fix of 7 CVEs","description":"- CVE-2026-53783: rrsync restricted-directory escape through a symlinked or\n  raced path component, --copy-unsafe-links, -D or a symlinked log file;\n  partial, the dir-merge rule escape needs --confine-root (3.5.0)\n- CVE-2026-53790: the daemon's pre-xfer/post-xfer exec hooks and RSYNC_CONNECT_PROG\n  expanded %RSYNC_*%/%H into a shell command without escaping them\n- CVE-2026-70453: unbounded hash_search() chain walk let a crafted run of equal weak\n  checksums pin the sender at 100% CPU; the per-offset walk is now bounded\n- CVE-2026-70456: heap out-of-bounds write in read_args() when the peer's argument count\n  lands exactly on the argv allocation; room for the trailing NULL is reserved\n- CVE-2026-70458: out-of-bounds write from a file entry marked FLAG_HLINKED accepted while\n  hard-link preservation was inactive; the flag is now gated and excludes dirs\n- CVE-2026-70462: a peer-supplied MSG_IO_TIMEOUT could disable or overflow the client's own\n  I/O timeout; non-positive values are ignored and the value is capped\n- CVE-2026-70464: the pre-transfer daemon handshake ran with no I/O timeout, so an\n  unauthenticated peer could hold every max-connections slot indefinitely\n- safe_arg() left an uninitialized heap byte in remote-shell filename args","status":"published","published":"2026-09-24T16:23:45Z","modified":"2026-10-26T09:30:54.910717183Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CLSA-2026-1791331076","title":"rsync: Fix of 5 CVEs","description":"- CVE-2026-53790: refuse a shell-active RSYNC_CONNECT_PROG %H host and\n  quote it; escape backtick, newline and carriage return in remote-shell\n  arguments\n- CVE-2026-53793: confine a \"/./\" inner-module chroot: secure\n  opens, change_dir, chmod, rename, delta-basis opens and alt-dest basis\n  stats, resolved with an in-tree-symlink-following walk so in-module\n  symlinks and --link-dest=../dir keep working; also sanitize a\n  fuzzy-basis xname on the client\n- CVE-2026-70453: cap the per-offset hash_search() chain walk at\n  MAX_CHAIN_LEN\n- CVE-2026-70458: refuse FLAG_HLINKED without -H or on a directory, and\n  skip the checksum basis match for a non-regular hard-linked entry\n- CVE-2026-70464: bound the daemon's pre-transfer handshake reads with an\n  absolute deadline and cap daemon argument lists\n- CVE-2026-29518: rebuild the module-relative path for the daemon\n  sender's confined open, fixing \"file has vanished\" for a file fetched\n  by name from a subdirectory of a \"use chroot = no\" module","status":"published","published":"2026-10-06T23:58:09Z","modified":"2026-10-26T09:43:54.391311126Z","updated_at":"2026-11-02T15:43:49.016976Z"},{"id":"CLSA-2026-1791331932","title":"rsync: Fix of 5 CVEs","description":"- CVE-2026-53790: refuse a shell-active RSYNC_CONNECT_PROG %H host and\n  quote it; escape backtick, newline and carriage return in remote-shell\n  arguments\n- CVE-2026-53793: confine a \"/./\" inner-module chroot: secure\n  opens, change_dir, chmod, rename, delta-basis opens and alt-dest basis\n  stats, resolved with an in-tree-symlink-following walk so in-module\n  symlinks and --link-dest=../dir keep working; also sanitize a\n  fuzzy-basis xname on the client\n- CVE-2026-70453: cap the per-offset hash_search() chain walk at\n  MAX_CHAIN_LEN\n- CVE-2026-70458: refuse FLAG_HLINKED without -H or on a directory, and\n  skip the checksum basis match for a non-regular hard-linked entry\n- CVE-2026-70464: bound the daemon's pre-transfer handshake reads with an\n  absolute deadline and cap daemon argument lists\n- CVE-2026-29518: rebuild the module-relative path for the daemon\n  sender's confined open, fixing \"file has vanished\" for a file fetched\n  by name from a subdirectory of a \"use chroot = no\" module","status":"published","published":"2026-10-08T22:07:12Z","modified":"2026-10-26T09:43:12.604117678Z","updated_at":"2026-11-02T15:43:49.016976Z"},{"id":"MGASA-2026-0487","title":"Updated rsync package fixes security vulnerabilities","description":"Several vulnerabilities were discovered in rsync, a fast, versatile,\nremote (and local) file-copying tool, which could result in local\nprivilege escalation, bypass of intended access restrictions,\ninformation disclosure, denial of service or the execution of arbitrary\ncode.\n","status":"published","published":"2026-10-12T18:47:12Z","modified":"2026-10-12T19:00:44.437948684Z","updated_at":"2026-11-02T15:49:43.795591Z"},{"id":"openSUSE-SU-2026:11869-1","title":"rsync-3.5.1-1.1 on GA media","description":"These are all security issues fixed in the rsync-3.5.1-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-09-23T00:00:00Z","modified":"2026-09-24T18:23:15.541661994Z","updated_at":"2026-11-02T16:58:40.245664Z"},{"id":"openSUSE-SU-2026:21650-1","title":"Security update for rsync","description":"This update for rsync fixes the following issues:\n\n- CVE-2026-53783: rrsync restricted-directory escape (validation-vs-exec race + unsafe option allowlist) (bsc#1269041).\n- CVE-2026-53784: Daemon module-root chdir escape under \"use chroot = no\" (bsc#1269042).\n- CVE-2026-53785: --relative implied-parent creation escapes the destination tree (bsc#1269043).\n- CVE-2026-53786: Daemon --filter merge file bypasses the module filter list (bsc#1269044).\n- CVE-2026-53788: Daemon name-converter accepts newline-bearing names into its line protocol (bsc#1269046).\n- CVE-2026-53789: Malicious sender expands --delete scope by reclassifying an implied parent (bsc#1269047).\n- CVE-2026-53790: Command / argument injection via unquoted peer- or host-controlled values (bsc#1269048).\n- CVE-2026-53791: PROXY-protocol mode lets a direct client spoof the daemon's source address (bsc#1269049).\n- CVE-2026-53792: Receiver-supplied zero checksum block length drives sender matching negative (bsc#1269050).\n- CVE-2026-53793: Chroot \"/./\" inner-module escape via a parent-component symlink (bsc#1269051).\n- CVE-2026-53794: Remote peer disables the per-allocation sanity cap via --max-alloc=0 (bsc#1269052).\n- CVE-2026-53795: Receiver write escape via an absolute --temp-dir / --link-dest disabling rename/link confinement\n  (bsc#1269053).\n- CVE-2026-53796: Non-daemon receiver destination-chdir symlink race (bsc#1269054).\n- CVE-2026-53797: Sender source-tree parent-component symlink race -\u003e out-of-tree disclosure (bsc#1269055).\n- CVE-2026-53798: Daemon name-converter empty response maps an unknown name to uid/gid 0 (bsc#1269045).\n- CVE-2026-53799: Receiver ACL/xattr application follows a symlink-race -\u003e arbitrary ACL set (bsc#1269056).\n- CVE-2026-53800: Sender --remove-source-files unlink follows a parent-component symlink race -\u003e arbitrary file deletion\n  outside the source tree (bsc#1269057).\n- CVE-2026-53801: Sender/daemon directory-scan enumeration escapes the transfer root / module -\u003e out-of-tree disclosure\n  (bsc#1269058).\n- CVE-2026-53802: Arbitrary file read / transfer-shaping via symlinked operator-supplied input files (bsc#1269039).\n- CVE-2026-53803: Arbitrary file write / privilege escalation via symlinked operator-supplied output paths\n  (bsc#1269040).\n- CVE-2026-70452: `hosts deny` fails OPEN when a configured hostname cannot be resolved, admitting the host it was meant\n  to block (bsc#1273441).\n- CVE-2026-70453: Quadratic CPU exhaustion in hash_search() from a crafted equal-weak-checksum chain (bsc#1273440).\n- CVE-2026-70454: rsync-ssl establishes an unauthenticated TLS connection (bsc#1273439).\n- CVE-2026-70455: Peer-controlled Zstandard worker exhaustion on an rsync daemon (bsc#1273438).\n- CVE-2026-70456: Remote out-of-bounds heap write in read_args() when the argument count lands exactly on maxargs\n  (bsc#1273437).\n- CVE-2026-70457: Attacker-chosen-offset write in parse_size_arg() error formatting (bsc#1273436).\n- CVE-2026-70458: Out-of-bounds write from a FLAG_HLINKED file entry accepted without -H (bsc#1273435).\n- CVE-2026-70459: Per-connection daemon child crash from a crafted first incremental file list with a non-directory\n  transfer root (bsc#1273434).\n- CVE-2026-70460: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-\n  module symlink (bsc#1273433).\n- CVE-2026-70461: Peer-driven one-byte heap out-of-bounds write in add_implied_include() (bsc#1273432).\n- CVE-2026-70462: Peer-supplied MSG_IO_TIMEOUT defeats the client's own I/O timeout (bsc#1273431).\n- CVE-2026-70463: \"auth users\" ignores documented comma-only parsing, silently skipping a deny/read-only rule\n  (bsc#1273430).\n- CVE-2026-70464: Unauthenticated pre-transfer handshake DoS locks out an rsync daemon module (bsc#1273429).\n","status":"published","published":"2026-08-26T12:30:55Z","modified":"2026-08-27T17:30:03.680559724Z","updated_at":"2026-11-02T16:58:41.885092Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2026-70458","title":"CVE-2026-70458 in rsync - Patched by Root","description":"Root has patched CVE-2026-70458 in the rsync package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-09-02T12:05:14Z","modified":"2026-09-02T14:00:08.433336204Z","updated_at":"2026-11-02T15:53:30.44348Z"},{"id":"SUSE-SU-2026:23253-1","title":"Security update for rsync","description":"This update for rsync fixes the following issues:\n\n- CVE-2026-53783: rrsync restricted-directory escape (bsc#1269041).\n- CVE-2026-53784: Daemon module-root chdir escape under \"use chroot = no\" (bsc#1269042).\n- CVE-2026-53785: --relative implied-parent creation escapes the destination tree (bsc#1269043).\n- CVE-2026-53786: Daemon --filter merge file bypasses the module filter list (bsc#1269044).\n- CVE-2026-53788: Daemon name-converter accepts newline-bearing names into its line protocol (bsc#1269046).\n- CVE-2026-53789: Malicious sender expands --delete scope by reclassifying an implied parent (bsc#1269047).\n- CVE-2026-53790: Command / argument injection via unquoted peer- or host-controlled values (bsc#1269048).\n- CVE-2026-53791: PROXY-protocol mode lets a direct client spoof the daemon's source address (bsc#1269049).\n- CVE-2026-53792: Receiver-supplied zero checksum block length drives sender matching negative (bsc#1269050).\n- CVE-2026-53793: Chroot \"/./\" inner-module escape via a parent-component symlink (bsc#1269051).\n- CVE-2026-53794: Remote peer disables the per-allocation sanity cap via --max-alloc=0 (bsc#1269052).\n- CVE-2026-53795: Receiver write escape via an absolute --temp-dir / --link-dest disabling rename/link confinement\n  (bsc#1269053).\n- CVE-2026-53796: Non-daemon receiver destination-chdir symlink race (bsc#1269054).\n- CVE-2026-53797: Sender source-tree parent-component symlink race -\u003e out-of-tree disclosure (bsc#1269055).\n- CVE-2026-53798: Daemon name-converter empty response maps an unknown name to uid/gid 0 (bsc#1269045).\n- CVE-2026-53799: Receiver ACL/xattr application follows a symlink-race -\u003e arbitrary ACL set (bsc#1269056).\n- CVE-2026-53800: Sender --remove-source-files unlink follows a parent-component symlink race -\u003e arbitrary file deletion\n  outside the source tree (bsc#1269057).\n- CVE-2026-53801: Sender/daemon directory-scan enumeration escapes the transfer root / module -\u003e out-of-tree disclosure\n  (bsc#1269058).\n- CVE-2026-53802: Arbitrary file read / transfer-shaping via symlinked operator-supplied input files (bsc#1269039).\n- CVE-2026-53803: Arbitrary file write / privilege escalation via symlinked operator-supplied output paths\n  (bsc#1269040).\n- CVE-2026-70452: `hosts deny` fails OPEN when a configured hostname cannot be resolved, admitting the host it was meant\n  to block (bsc#1273441).\n- CVE-2026-70453: Quadratic CPU exhaustion in hash_search() from a crafted equal-weak-checksum chain (bsc#1273440).\n- CVE-2026-70454: rsync-ssl establishes an unauthenticated TLS connection (bsc#1273439).\n- CVE-2026-70455: Peer-controlled Zstandard worker exhaustion on an rsync daemon (bsc#1273438).\n- CVE-2026-70456: Remote out-of-bounds heap write in read_args() when the argument count lands exactly on maxargs\n  (bsc#1273437).\n- CVE-2026-70457: Attacker-chosen-offset write in parse_size_arg() error formatting (bsc#1273436).\n- CVE-2026-70458: Out-of-bounds write from a FLAG_HLINKED file entry accepted without -H (bsc#1273435).\n- CVE-2026-70459: Per-connection daemon child crash from a crafted first incremental file list with a non-directory\n  transfer root (bsc#1273434).\n- CVE-2026-70460: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-\n  module symlink (bsc#1273433).\n- CVE-2026-70461: Peer-driven one-byte heap out-of-bounds write in add_implied_include() (bsc#1273432).\n- CVE-2026-70462: Peer-supplied MSG_IO_TIMEOUT defeats the client's own I/O timeout (bsc#1273431).\n- CVE-2026-70463: \"auth users\" ignores documented comma-only parsing, silently skipping a deny/read-only rule\n  (bsc#1273430).\n- CVE-2026-70464: Unauthenticated pre-transfer handshake DoS locks out an rsync daemon module (bsc#1273429).\n","status":"published","published":"2026-08-24T14:42:20Z","modified":"2026-08-27T18:23:12.181176422Z","updated_at":"2026-11-02T15:54:03.503431Z"},{"id":"SUSE-SU-2026:23254-1","title":"Security update for rsync","description":"This update for rsync fixes the following issues:\n\n- CVE-2026-53783: rrsync restricted-directory escape (validation-vs-exec race + unsafe option allowlist) (bsc#1269041).\n- CVE-2026-53784: Daemon module-root chdir escape under \"use chroot = no\" (bsc#1269042).\n- CVE-2026-53785: --relative implied-parent creation escapes the destination tree (bsc#1269043).\n- CVE-2026-53786: Daemon --filter merge file bypasses the module filter list (bsc#1269044).\n- CVE-2026-53788: Daemon name-converter accepts newline-bearing names into its line protocol (bsc#1269046).\n- CVE-2026-53789: Malicious sender expands --delete scope by reclassifying an implied parent (bsc#1269047).\n- CVE-2026-53790: Command / argument injection via unquoted peer- or host-controlled values (bsc#1269048).\n- CVE-2026-53791: PROXY-protocol mode lets a direct client spoof the daemon's source address (bsc#1269049).\n- CVE-2026-53792: Receiver-supplied zero checksum block length drives sender matching negative (bsc#1269050).\n- CVE-2026-53793: Chroot \"/./\" inner-module escape via a parent-component symlink (bsc#1269051).\n- CVE-2026-53794: Remote peer disables the per-allocation sanity cap via --max-alloc=0 (bsc#1269052).\n- CVE-2026-53795: Receiver write escape via an absolute --temp-dir / --link-dest disabling rename/link confinement\n  (bsc#1269053).\n- CVE-2026-53796: Non-daemon receiver destination-chdir symlink race (TOCTOU) (bsc#1269054).\n- CVE-2026-53797: Sender source-tree parent-component symlink race -\u003e out-of-tree disclosure (bsc#1269055).\n- CVE-2026-53798: Daemon name-converter empty response maps an unknown name to uid/gid 0 (bsc#1269045).\n- CVE-2026-53799: Receiver ACL/xattr application follows a symlink-race -\u003e arbitrary ACL set (local privilege\n  escalation) (bsc#1269056).\n- CVE-2026-53800: Sender --remove-source-files unlink follows a parent-component symlink race -\u003e arbitrary file deletion\n  outside the source tree (bsc#1269057).\n- CVE-2026-53801: Sender/daemon directory-scan enumeration escapes the transfer root / module -\u003e out-of-tree disclosure\n  (bsc#1269058).\n- CVE-2026-53802: Arbitrary file read / transfer-shaping via symlinked operator-supplied input files (bsc#1269039).\n- CVE-2026-53803: Arbitrary file write / privilege escalation via symlinked operator-supplied output paths\n  (bsc#1269040).\n- CVE-2026-70452: `hosts deny` fails OPEN when a configured hostname cannot be resolved, admitting the host it was meant\n  to block (bsc#1273441).\n- CVE-2026-70453: Quadratic CPU exhaustion in hash_search() from a crafted equal-weak-checksum chain (bsc#1273440).\n- CVE-2026-70454: rsync-ssl establishes an unauthenticated TLS connection (bsc#1273439).\n- CVE-2026-70455: Peer-controlled Zstandard worker exhaustion on an rsync daemon (bsc#1273438).\n- CVE-2026-70456: Remote out-of-bounds heap write in read_args() when the argument count lands exactly on maxargs\n  (bsc#1273437).\n- CVE-2026-70457: Attacker-chosen-offset write in parse_size_arg() error formatting (bsc#1273436).\n- CVE-2026-70458: Out-of-bounds write from a FLAG_HLINKED file entry accepted without -H (bsc#1273435).\n- CVE-2026-70459: Per-connection daemon child crash from a crafted first incremental file list with a non-directory\n  transfer root (bsc#1273434).\n- CVE-2026-70460: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-\n  module symlink (bsc#1273433).\n- CVE-2026-70461: Peer-driven one-byte heap out-of-bounds write in add_implied_include() (bsc#1273432).\n- CVE-2026-70462: Peer-supplied MSG_IO_TIMEOUT defeats the client's own I/O timeout (bsc#1273431).\n- CVE-2026-70463: \"auth users\" ignores documented comma-only parsing, silently skipping a deny/read-only rule\n  (bsc#1273430).\n- CVE-2026-70464: Unauthenticated pre-transfer handshake DoS locks out an rsync daemon module (bsc#1273429).\n","status":"published","published":"2026-08-24T14:41:03Z","modified":"2026-08-31T18:23:08.005451973Z","updated_at":"2026-11-02T15:54:03.503431Z"},{"id":"SUSE-SU-2026:23289-1","title":"Security update for rsync","description":"This update for rsync fixes the following issues:\n\n- CVE-2026-53783: rrsync restricted-directory escape (validation-vs-exec race + unsafe option allowlist) (bsc#1269041).\n- CVE-2026-53784: Daemon module-root chdir escape under \"use chroot = no\" (bsc#1269042).\n- CVE-2026-53785: --relative implied-parent creation escapes the destination tree (bsc#1269043).\n- CVE-2026-53786: Daemon --filter merge file bypasses the module filter list (bsc#1269044).\n- CVE-2026-53788: Daemon name-converter accepts newline-bearing names into its line protocol (bsc#1269046).\n- CVE-2026-53789: Malicious sender expands --delete scope by reclassifying an implied parent (bsc#1269047).\n- CVE-2026-53790: Command / argument injection via unquoted peer- or host-controlled values (bsc#1269048).\n- CVE-2026-53791: PROXY-protocol mode lets a direct client spoof the daemon's source address (bsc#1269049).\n- CVE-2026-53792: Receiver-supplied zero checksum block length drives sender matching negative (bsc#1269050).\n- CVE-2026-53793: Chroot \"/./\" inner-module escape via a parent-component symlink (bsc#1269051).\n- CVE-2026-53794: Remote peer disables the per-allocation sanity cap via --max-alloc=0 (bsc#1269052).\n- CVE-2026-53795: Receiver write escape via an absolute --temp-dir / --link-dest disabling rename/link confinement\n  (bsc#1269053).\n- CVE-2026-53796: Non-daemon receiver destination-chdir symlink race (bsc#1269054).\n- CVE-2026-53797: Sender source-tree parent-component symlink race -\u003e out-of-tree disclosure (bsc#1269055).\n- CVE-2026-53798: Daemon name-converter empty response maps an unknown name to uid/gid 0 (bsc#1269045).\n- CVE-2026-53799: Receiver ACL/xattr application follows a symlink-race -\u003e arbitrary ACL set (bsc#1269056).\n- CVE-2026-53800: Sender --remove-source-files unlink follows a parent-component symlink race -\u003e arbitrary file deletion\n  outside the source tree (bsc#1269057).\n- CVE-2026-53801: Sender/daemon directory-scan enumeration escapes the transfer root / module -\u003e out-of-tree disclosure\n  (bsc#1269058).\n- CVE-2026-53802: Arbitrary file read / transfer-shaping via symlinked operator-supplied input files (bsc#1269039).\n- CVE-2026-53803: Arbitrary file write / privilege escalation via symlinked operator-supplied output paths\n  (bsc#1269040).\n- CVE-2026-70452: `hosts deny` fails OPEN when a configured hostname cannot be resolved, admitting the host it was meant\n  to block (bsc#1273441).\n- CVE-2026-70453: Quadratic CPU exhaustion in hash_search() from a crafted equal-weak-checksum chain (bsc#1273440).\n- CVE-2026-70454: rsync-ssl establishes an unauthenticated TLS connection (bsc#1273439).\n- CVE-2026-70455: Peer-controlled Zstandard worker exhaustion on an rsync daemon (bsc#1273438).\n- CVE-2026-70456: Remote out-of-bounds heap write in read_args() when the argument count lands exactly on maxargs\n  (bsc#1273437).\n- CVE-2026-70457: Attacker-chosen-offset write in parse_size_arg() error formatting (bsc#1273436).\n- CVE-2026-70458: Out-of-bounds write from a FLAG_HLINKED file entry accepted without -H (bsc#1273435).\n- CVE-2026-70459: Per-connection daemon child crash from a crafted first incremental file list with a non-directory\n  transfer root (bsc#1273434).\n- CVE-2026-70460: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-\n  module symlink (bsc#1273433).\n- CVE-2026-70461: Peer-driven one-byte heap out-of-bounds write in add_implied_include() (bsc#1273432).\n- CVE-2026-70462: Peer-supplied MSG_IO_TIMEOUT defeats the client's own I/O timeout (bsc#1273431).\n- CVE-2026-70463: \"auth users\" ignores documented comma-only parsing, silently skipping a deny/read-only rule\n  (bsc#1273430).\n- CVE-2026-70464: Unauthenticated pre-transfer handshake DoS locks out an rsync daemon module (bsc#1273429).\n","status":"published","published":"2026-08-26T12:30:35Z","modified":"2026-09-04T18:23:13.554181498Z","updated_at":"2026-11-02T15:54:03.503431Z"},{"id":"SUSE-SU-2026:23323-1","title":"Security update for rsync","description":"This update for rsync fixes the following issues:\n\n- CVE-2026-53783: rrsync restricted-directory escape (validation-vs-exec race + unsafe option allowlist) (bsc#1269041).\n- CVE-2026-53784: Daemon module-root chdir escape under \"use chroot = no\" (bsc#1269042).\n- CVE-2026-53785: --relative implied-parent creation escapes the destination tree (bsc#1269043).\n- CVE-2026-53786: Daemon --filter merge file bypasses the module filter list (bsc#1269044).\n- CVE-2026-53788: Daemon name-converter accepts newline-bearing names into its line protocol (bsc#1269046).\n- CVE-2026-53789: Malicious sender expands --delete scope by reclassifying an implied parent (bsc#1269047).\n- CVE-2026-53790: Command / argument injection via unquoted peer- or host-controlled values (bsc#1269048).\n- CVE-2026-53791: PROXY-protocol mode lets a direct client spoof the daemon's source address (bsc#1269049).\n- CVE-2026-53792: Receiver-supplied zero checksum block length drives sender matching negative (bsc#1269050).\n- CVE-2026-53793: Chroot \"/./\" inner-module escape via a parent-component symlink (bsc#1269051).\n- CVE-2026-53794: Remote peer disables the per-allocation sanity cap via --max-alloc=0 (bsc#1269052).\n- CVE-2026-53795: Receiver write escape via an absolute --temp-dir / --link-dest disabling rename/link confinement\n  (bsc#1269053).\n- CVE-2026-53796: Non-daemon receiver destination-chdir symlink race (bsc#1269054).\n- CVE-2026-53797: Sender source-tree parent-component symlink race -\u003e out-of-tree disclosure (bsc#1269055).\n- CVE-2026-53798: Daemon name-converter empty response maps an unknown name to uid/gid 0 (bsc#1269045).\n- CVE-2026-53799: Receiver ACL/xattr application follows a symlink-race -\u003e arbitrary ACL set (bsc#1269056).\n- CVE-2026-53800: Sender --remove-source-files unlink follows a parent-component symlink race -\u003e arbitrary file deletion\n  outside the source tree (bsc#1269057).\n- CVE-2026-53801: Sender/daemon directory-scan enumeration escapes the transfer root / module -\u003e out-of-tree disclosure\n  (bsc#1269058).\n- CVE-2026-53802: Arbitrary file read / transfer-shaping via symlinked operator-supplied input files (bsc#1269039).\n- CVE-2026-53803: Arbitrary file write / privilege escalation via symlinked operator-supplied output paths\n  (bsc#1269040).\n- CVE-2026-70452: `hosts deny` fails OPEN when a configured hostname cannot be resolved, admitting the host it was meant\n  to block (bsc#1273441).\n- CVE-2026-70453: Quadratic CPU exhaustion in hash_search() from a crafted equal-weak-checksum chain (bsc#1273440).\n- CVE-2026-70454: rsync-ssl establishes an unauthenticated TLS connection (bsc#1273439).\n- CVE-2026-70455: Peer-controlled Zstandard worker exhaustion on an rsync daemon (bsc#1273438).\n- CVE-2026-70456: Remote out-of-bounds heap write in read_args() when the argument count lands exactly on maxargs\n  (bsc#1273437).\n- CVE-2026-70457: Attacker-chosen-offset write in parse_size_arg() error formatting (bsc#1273436).\n- CVE-2026-70458: Out-of-bounds write from a FLAG_HLINKED file entry accepted without -H (bsc#1273435).\n- CVE-2026-70459: Per-connection daemon child crash from a crafted first incremental file list with a non-directory\n  transfer root (bsc#1273434).\n- CVE-2026-70460: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-\n  module symlink (bsc#1273433).\n- CVE-2026-70461: Peer-driven one-byte heap out-of-bounds write in add_implied_include() (bsc#1273432).\n- CVE-2026-70462: Peer-supplied MSG_IO_TIMEOUT defeats the client's own I/O timeout (bsc#1273431).\n- CVE-2026-70463: \"auth users\" ignores documented comma-only parsing, silently skipping a deny/read-only rule\n  (bsc#1273430).\n- CVE-2026-70464: Unauthenticated pre-transfer handshake DoS locks out an rsync daemon module (bsc#1273429).\n","status":"published","published":"2026-08-26T12:30:35Z","modified":"2026-09-10T18:23:10.543995859Z","updated_at":"2026-11-02T15:54:03.503431Z"},{"id":"SUSE-SU-2026:3634-1","title":"Security update for rsync","description":"This update for rsync fixes the following issues:\n\n- CVE-2026-53783: rrsync restricted-directory escape (validation-vs-exec race + unsafe option allowlist) (bsc#1269041).\n- CVE-2026-53784: Daemon module-root chdir escape under 'use chroot = no' (bsc#1269042).\n- CVE-2026-53785: --relative implied-parent creation escapes the destination tree (bsc#1269043).\n- CVE-2026-53786: Daemon --filter merge file bypasses the module filter list (bsc#1269044).\n- CVE-2026-53788: Daemon name-converter accepts newline-bearing names into its line protocol (bsc#1269046).\n- CVE-2026-53789: Malicious sender expands --delete scope by reclassifying an implied parent (bsc#1269047).\n- CVE-2026-53790: Command / argument injection via unquoted peer- or host-controlled values (bsc#1269048).\n- CVE-2026-53791: PROXY-protocol mode lets a direct client spoof the daemon's source address (bsc#1269049).\n- CVE-2026-53792: Receiver-supplied zero checksum block length drives sender matching negative (bsc#1269050).\n- CVE-2026-53793: Chroot '/./' inner-module escape via a parent-component symlink (bsc#1269051).\n- CVE-2026-53794: Remote peer disables the per-allocation sanity cap via --max-alloc=0 (bsc#1269052).\n- CVE-2026-53795: Receiver write escape via an absolute --temp-dir / --link-dest disabling rename/link confinement\n  (bsc#1269053).\n- CVE-2026-53796: Non-daemon receiver destination-chdir symlink race (TOCTOU) (bsc#1269054).\n- CVE-2026-53797: Sender source-tree parent-component symlink race -\u003e out-of-tree disclosure (bsc#1269055).\n- CVE-2026-53798: Daemon name-converter empty response maps an unknown name to uid/gid 0 (bsc#1269045).\n- CVE-2026-53799: Receiver ACL/xattr application follows a symlink-race -\u003e arbitrary ACL set (local privilege\n  escalation) (bsc#1269056).\n- CVE-2026-53800: Sender --remove-source-files unlink follows a parent-component symlink race -\u003e arbitrary file deletion\n  outside the source tree (bsc#1269057).\n- CVE-2026-53801: Sender/daemon directory-scan enumeration escapes the transfer root / module -\u003e out-of-tree disclosure\n  (bsc#1269058).\n- CVE-2026-53802: Arbitrary file read / transfer-shaping via symlinked operator-supplied input files (bsc#1269039).\n- CVE-2026-53803: Arbitrary file write / privilege escalation via symlinked operator-supplied output paths\n  (bsc#1269040).\n- CVE-2026-70452: `hosts deny` fails OPEN when a configured hostname cannot be resolved, admitting the host it was meant\n  to block (bsc#1273441).\n- CVE-2026-70453: Quadratic CPU exhaustion in hash_search() from a crafted equal-weak-checksum chain (bsc#1273440).\n- CVE-2026-70454: rsync-ssl establishes an unauthenticated TLS connection (bsc#1273439).\n- CVE-2026-70455: Peer-controlled Zstandard worker exhaustion on an rsync daemon (bsc#1273438).\n- CVE-2026-70456: Remote out-of-bounds heap write in read_args() when the argument count lands exactly on maxargs\n  (bsc#1273437).\n- CVE-2026-70457: Attacker-chosen-offset write in parse_size_arg() error formatting (bsc#1273436).\n- CVE-2026-70458: Out-of-bounds write from a FLAG_HLINKED file entry accepted without -H (bsc#1273435).\n- CVE-2026-70459: Per-connection daemon child crash from a crafted first incremental file list with a non-directory\n  transfer root (bsc#1273434).\n- CVE-2026-70460: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-\n  module symlink (bsc#1273433).\n- CVE-2026-70461: Peer-driven one-byte heap out-of-bounds write in add_implied_include() (bsc#1273432).\n- CVE-2026-70462: Peer-supplied MSG_IO_TIMEOUT defeats the client's own I/O timeout (bsc#1273431).\n- CVE-2026-70463: 'auth users' ignores documented comma-only parsing, silently skipping a deny/read-only rule\n  (bsc#1273430).\n- CVE-2026-70464: Unauthenticated pre-transfer handshake DoS locks out an rsync daemon module (bsc#1273429).\n","status":"published","published":"2026-08-17T19:03:56Z","modified":"2026-08-18T09:30:04.645936343Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:3657-1","title":"Security update for rsync","description":"This update for rsync fixes the following issues:\n\n- CVE-2026-53783: rrsync restricted-directory escape (validation-vs-exec race + unsafe option allowlist) (bsc#1269041).\n- CVE-2026-53784: Daemon module-root chdir escape under 'use chroot = no' (bsc#1269042).\n- CVE-2026-53785: --relative implied-parent creation escapes the destination tree (bsc#1269043).\n- CVE-2026-53786: Daemon --filter merge file bypasses the module filter list (bsc#1269044).\n- CVE-2026-53788: Daemon name-converter accepts newline-bearing names into its line protocol (bsc#1269046).\n- CVE-2026-53789: Malicious sender expands --delete scope by reclassifying an implied parent (bsc#1269047).\n- CVE-2026-53790: Command / argument injection via unquoted peer- or host-controlled values (bsc#1269048).\n- CVE-2026-53791: PROXY-protocol mode lets a direct client spoof the daemon's source address (bsc#1269049).\n- CVE-2026-53792: Receiver-supplied zero checksum block length drives sender matching negative (bsc#1269050).\n- CVE-2026-53793: Chroot '/./' inner-module escape via a parent-component symlink (bsc#1269051).\n- CVE-2026-53794: Remote peer disables the per-allocation sanity cap via --max-alloc=0 (bsc#1269052).\n- CVE-2026-53795: Receiver write escape via an absolute --temp-dir / --link-dest disabling rename/link confinement\n  (bsc#1269053).\n- CVE-2026-53796: Non-daemon receiver destination-chdir symlink race (TOCTOU) (bsc#1269054).\n- CVE-2026-53797: Sender source-tree parent-component symlink race -\u003e out-of-tree disclosure (bsc#1269055).\n- CVE-2026-53798: Daemon name-converter empty response maps an unknown name to uid/gid 0 (bsc#1269045).\n- CVE-2026-53799: Receiver ACL/xattr application follows a symlink-race -\u003e arbitrary ACL set (local privilege\n  escalation) (bsc#1269056).\n- CVE-2026-53800: Sender --remove-source-files unlink follows a parent-component symlink race -\u003e arbitrary file deletion\n  outside the source tree (bsc#1269057).\n- CVE-2026-53801: Sender/daemon directory-scan enumeration escapes the transfer root / module -\u003e out-of-tree disclosure\n  (bsc#1269058).\n- CVE-2026-53802: Arbitrary file read / transfer-shaping via symlinked operator-supplied input files (bsc#1269039).\n- CVE-2026-53803: Arbitrary file write / privilege escalation via symlinked operator-supplied output paths\n  (bsc#1269040).\n- CVE-2026-70452: `hosts deny` fails OPEN when a configured hostname cannot be resolved, admitting the host it was meant\n  to block (bsc#1273441).\n- CVE-2026-70453: Quadratic CPU exhaustion in hash_search() from a crafted equal-weak-checksum chain (bsc#1273440).\n- CVE-2026-70454: rsync-ssl establishes an unauthenticated TLS connection (bsc#1273439).\n- CVE-2026-70455: Peer-controlled Zstandard worker exhaustion on an rsync daemon (bsc#1273438).\n- CVE-2026-70456: Remote out-of-bounds heap write in read_args() when the argument count lands exactly on maxargs\n  (bsc#1273437).\n- CVE-2026-70457: Attacker-chosen-offset write in parse_size_arg() error formatting (bsc#1273436).\n- CVE-2026-70458: Out-of-bounds write from a FLAG_HLINKED file entry accepted without -H (bsc#1273435).\n- CVE-2026-70459: Per-connection daemon child crash from a crafted first incremental file list with a non-directory\n  transfer root (bsc#1273434).\n- CVE-2026-70460: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-\n  module symlink (bsc#1273433).\n- CVE-2026-70461: Peer-driven one-byte heap out-of-bounds write in add_implied_include() (bsc#1273432).\n- CVE-2026-70462: Peer-supplied MSG_IO_TIMEOUT defeats the client's own I/O timeout (bsc#1273431).\n- CVE-2026-70463: 'auth users' ignores documented comma-only parsing, silently skipping a deny/read-only rule\n  (bsc#1273430).\n- CVE-2026-70464: Unauthenticated pre-transfer handshake DoS locks out an rsync daemon module (bsc#1273429).\n","status":"published","published":"2026-08-20T17:06:16Z","modified":"2026-08-21T09:15:06.399709911Z","updated_at":"2026-11-02T15:54:05.392906Z"}]}}