rsync < 3.5.0 Privilege Confusion via name-converter uid/gid mapping
CVE-2026-53798 is fixed in 4 products on 1 platform, first by SUSE-SU-2026:3657-1, released August 20, 2026. It is not reported as exploited. Patch Radar priority: Routine.
rsync 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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| rsync · Debian 13.5 (trixie) | 3.5.0+ds1-0+deb13u1 | DEBIAN-CVE-2026-53798 | Aug 27, 2026 |
| rsync · Debian 14 | 3.5.0+ds1-1 | DEBIAN-CVE-2026-53798 | Aug 27, 2026 |
| rsync · amzn 2023 | 3.5.1-1.amzn2023.0.1 | ALAS2023-2026-3131 | Sep 28, 2026 |
| rsync · opensuse-leap 16.0 | 3.4.1-160000.6.1 | OPENSUSE-SU-2026:21650-1 | Aug 26, 2026 |
| rsync · sles 15.6 | 3.2.7-150600.3.24.1 | SUSE-SU-2026:3657-1 | Aug 20, 2026 |
| rsync · sles 15.7 | 3.2.7-150600.3.24.1 | SUSE-SU-2026:3657-1 | Aug 20, 2026 |
| rsync · sles 16.0 | 3.4.1-160000.6.1 | SUSE-SU-2026:23323-1 | Aug 26, 2026 |
| rsync-daemon · amzn 2023 | 3.5.1-1.amzn2023.0.1 | ALAS2023-2026-3131 | Sep 28, 2026 |
| rsync-debuginfo · amzn 2023 | 3.5.1-1.amzn2023.0.1 | ALAS2023-2026-3131 | Sep 28, 2026 |
| rsync-debugsource · amzn 2023 | 3.5.1-1.amzn2023.0.1 | ALAS2023-2026-3131 | Sep 28, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.