Quick answers
- Is CVE-2026-43619 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-43619 being exploited in the wild.
- How severe is CVE-2026-43619?
- Medium severity, with a CVSS score of 6.3, published 20 May 2026.
- Which products and versions are affected?
- RsyncProject Rsync <= 3.4.2.
- Is there a fix for CVE-2026-43619?
- 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-43619 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-43619?
- 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
Rsync is vulnerable to a Time-of-Check Time-of-Use (TOCTOU) race condition during path-based system calls such as chmod, lchown, utimes, and rename. When an rsync daemon is configured with 'use chroot = no', a local attacker can exploit the timing window between path resolution and syscall execution by swapping symlinks. This allows the attacker to redirect file operations to arbitrary locations outside the intended module boundary, applying sender-supplied permissions, ownership, or filenames to sensitive system files. The issue is addressed in version 3.4.3 by utilizing more secure file handling methods like openat2 with RESOLVE_BENEATH where available.
Affected products
- RsyncProject rsync <= 3.4.2
Timeline
- 2026-05-19: disclosed
- 2026-05-20: patched: Fixed in version 3.4.3
- 2026-05-20: advisory