# CVE-2026-53798: rsync < 3.5.0 Privilege Confusion via name-converter uid/gid mapping

> Local attackers can cause transferred files to be owned by root by manipulating name-converter responses, leading to privilege escalation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** ALPINE-CVE-2026-53798, AZL-95804, BELL-CVE-2026-53798, DEBIAN-CVE-2026-53798, ECHO-2583-309c-2ae2, GHSA-hx7p-3gvv-pqgv, UBUNTU-CVE-2026-53798

## What is CVE-2026-53798?

CVE-2026-53798 is a medium-severity vulnerability in RsyncProject rsync, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-704 (Incorrect Type Conversion or Cast)

## Which versions are affected by CVE-2026-53798?

It affects 1 product.


Products: Samba Rsync.

## How do I fix CVE-2026-53798?

Upgrade to a fixed version.

## Is CVE-2026-53798 being exploited?

There is no known exploitation of CVE-2026-53798 in the wild and no public exploit code.

## Other vulnerabilities in RsyncProject rsync

- [CVE-2017-15994](https://insights.sbomify.com/CVE-2017-15994/): Security feature bypass in n/a (critical 9.8)
- [CVE-2026-53791](https://insights.sbomify.com/CVE-2026-53791/): rsync < 3.5.0 Daemon IP Spoofing via PROXY Protocol Header (critical 9.1)
- [CVE-2026-70461](https://insights.sbomify.com/CVE-2026-70461/): rsync 3.2.5 < 3.5.0 Heap Out-of-Bounds Write via files-from Entry (high 8.8)
- [CVE-2026-70455](https://insights.sbomify.com/CVE-2026-70455/): rsync 3.4.2 < 3.5.0 DoS via --zt Zstandard Compression Thread Exhaustion (high 8.7)
- [CVE-2026-70463](https://insights.sbomify.com/CVE-2026-70463/): rsync 3.1.0 < 3.5.0 Authorization Bypass via auth users Directive Parsing (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53798 and fix it if it is affected.

What it is: CVE-2026-53798 is a medium-severity vulnerability in RsyncProject rsync, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53798 in the wild and no public exploit code.

Affected product: RsyncProject rsync. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53798/ (Markdown: https://insights.sbomify.com/CVE-2026-53798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53798
- OSV: https://osv.dev/vulnerability/CVE-2026-53798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53798/
Summaries are generated and may contain mistakes; the official description above is the record.