CVE-2026-43619: Rsync < 3.4.3 Symlink Race Condition via Path-Based Syscalls

Published May 20, 2026
·
Updated

Last updated 2 June 2026

Other sources

Rsync < 3.4.3 Symlink Race Condition via Path-Based Syscalls

Microsoft

Rsync version 3.4.2 and prior contain symlink race condition vulnerabilities in path-based system calls including chmod, lchown, utimes, rename, unlink, mkdir, symlink, mknod, link, rmdir, and lstat that allow local attackers to redirect operations to files outside the exported rsync module. Attackers with local filesystem access can exploit the timing window between path resolution and syscall execution by swapping symlinks to apply sender-supplied permissions, ownership, timestamps, or filenames to arbitrary files outside the intended module boundary on rsync daemons configured with 'use chroot = no'.

Launchpad

Affected Software

4 affected componentsFixes available
rsync rsync<3.4.3
Samba rsync<=3.4.2
Microsoft azl3 rsync 3.4.1-2
debian/rsync<=3.2.3-4+deb11u1, <=3.2.7-1+deb12u4, <=3.4.1+ds1-5+deb13u2
3.2.3-4+deb11u43.2.7-1+deb12u53.4.1+ds1-5+deb13u33.4.3+ds1-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/rsync to a version that resolves this vulnerability.

    Fixed in 3.2.3-4+deb11u4Fixed in 3.2.7-1+deb12u5Fixed in 3.4.1+ds1-5+deb13u3Fixed in 3.4.3+ds1-2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.4.3
  3. Configuration

    For rsync daemons configured with 'use chroot = no', change configuration to enable chroot (i.e., do not use 'use chroot = no') to reduce the symlink race condition impact that allows operations to be redirected outside the exported module boundary.

    rsync daemon use chroot = no
  4. Compensating control

    If local filesystem access is possible, restrict local access to the rsync daemon’s filesystem/module paths (e.g., via OS permissions/ACLs or isolation) to prevent attackers from swapping symlinks during the timing window between path resolution and syscall execution.

Event History

May 20, 2026
CVE Published
via MITRE·12:49 AM
Data Sourced
via MITRE·12:49 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Launchpad·02:42 PM
Description
May 21, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Jun 1, 2026
Data Sourced
via Debian·11:32 AM
DescriptionAffected Software
Jun 2, 2026
Data Sourced
via Ubuntu·11:33 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-43619?

CVE-2026-43619 is classified as a medium severity vulnerability due to the potential for local attackers to exploit symlink race conditions.

2

How do I fix CVE-2026-43619?

To fix CVE-2026-43619, upgrade Rsync to version 3.4.3 or later to mitigate the vulnerability.

3

What versions of Rsync are affected by CVE-2026-43619?

Rsync versions prior to 3.4.3, specifically up to and including 3.4.2, are affected by CVE-2026-43619.

4

What type of vulnerability is CVE-2026-43619?

CVE-2026-43619 is a symlink race condition vulnerability that affects path-based system calls in Rsync.

5

Who can exploit CVE-2026-43619?

CVE-2026-43619 can potentially be exploited by local attackers who have access to the system running a vulnerable version of Rsync.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203