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

> Local attackers can exploit a symlink race condition in rsync to modify arbitrary files outside the module boundary when chroot is disabled.

- **Severity:** High 7.2 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** ALPINE-CVE-2026-43619, AZL-86985, BELL-CVE-2026-43619, CLSA-2026-1779959867, CLSA-2026-1780486587, CVE-2026-44509, DEBIAN-CVE-2026-43619, ECHO-2de0-1b04-bad9, GHSA-4h9m-w5ff-j735, GHSA-pwrq-5rj3-c43m, JLSEC-2026-630, UBUNTU-CVE-2026-43619

## What is CVE-2026-43619?

CVE-2026-43619 is a high-severity vulnerability in RsyncProject rsync, published on 20 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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'.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 1 product.


Products: Samba Rsync.

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

Upgrade to a fixed version.

## Is CVE-2026-43619 being exploited?

There is no known exploitation of CVE-2026-43619 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-43619 and fix it if it is affected.

What it is: CVE-2026-43619 is a high-severity vulnerability in RsyncProject rsync, published on 20 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43619 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-43619/ (Markdown: https://insights.sbomify.com/CVE-2026-43619/index.md)
```

## Sources

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

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