Quick answers
- Is CVE-2026-29518 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-29518 being exploited in the wild.
- How severe is CVE-2026-29518?
- High severity, with a CVSS score of 7, published 20 May 2026.
- Which products and versions are affected?
- RsyncProject Rsync < 3.4.3.
- Is there a fix for CVE-2026-29518?
- A patch was published on 2026-05-20: Fixed in version 3.4.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-29518 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-29518?
- Check whether you run RsyncProject Rsync at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A time-of-check to time-of-use (TOCTOU) race condition exists in the rsync daemon's file handling logic. An attacker with write access to a module path can replace parent directory components with symbolic links during the small window between the daemon's path validation and the actual file operation. This allows the attacker to redirect file writes to arbitrary locations on the filesystem. The vulnerability is exploitable only when the 'chroot' setting is set to false. If the daemon is running with elevated privileges, this can result in arbitrary file creation or modification, leading to privilege escalation. The issue is addressed in version 3.4.3.
Affected products
- RsyncProject rsync < 3.4.3
Timeline
- 2026-05-20: disclosed
- 2026-05-20: patched: Fixed in version 3.4.3
- 2026-05-20: advisory