Servers and applications
CVE-2026-53795
rsync: receiver write escape via an absolute --temp-dir / --link-dest disabling rename/link confinement
- Severity
- High 7.2
- Published
- 13 Aug 2026
- Last changed
- 24 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.5.0
- Exploit chance
- 0.4% in the next 30 daysHigher than 34% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Link following (CWE-59)
- Attack
- Over the network · No login needed · Needs someone to view a page or file
- Attacker can
- Change data · Take it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Also known as
- GHSA-m9vj-637x-v6pq
- Sources
- NVD, Project advisories (GitHub)
Description
do_rename_at()/do_link_at() confine a relative destination beneath the tree, but bailed to the unconfined path-based do_rename()/do_link() whenever EITHER path was absolute. An absolute source -- an absolute --temp-dir temp file, or an absolute --link-dest basis -- therefore disabled confinement of the relative destination, so finish_transfer()'s tmp->final rename (and a hard-link create) followed a destination parent component an attacker flipped from a directory to a symlink mid-transfer, landing the transferred file OUTSIDE the destination tree (arbitrary write / local privilege escalation).
The same wrappers had a second confinement gap of the same shape: a path with no slash (a bare top-level name) made the WHOLE rename/link fall through to the unconfined do_rename()/do_link(), so a mixed-parent operation (one slashed path, one bare path) escaped confinement on the slashed side too. Both gaps are closed by the same fix and are covered by this item.
Affected software
| Software | Affected versions |
|---|---|
rsyncServers and applications · cpe:a:samba:rsync |
|
rsyncServers and applications · github:rsyncproject/rsync |
|
About rsync
file synchronization protocol and software
- GitHub stars
- 5,367GitHub, 15 Nov 2026
- Forks
- 631GitHub, 15 Nov 2026
- Latest release
- v3.5.2GitHub, 15 Nov 2026
- Released
- 3 Nov 2026GitHub
- Developer
- Andrew TridgellWikidata
- Written in
- CWikidata
- First released
- 19 Jun 1996Wikidata
- First published on GitHub
- 25 May 2020GitHub
Vulnerabilities in rsync
- In our list
- 58
- Published in the last 12 months
- 41
- Critical, last 12 months
- 5
- High, last 12 months
- 22
- Known exploited
- 0
- CVE-2026-119741Crafted checksum collisions can exhaust sender CPUHigh 8.7 3 Nov 2026
- CVE-2026-70464rsync: Unauthenticated pre-transfer handshake DoS locks out an rsync daemon moduleHigh 8.7 13 Aug 2026
- CVE-2026-70463rsync: "auth users" ignores documented comma-only parsing, silently skipping a deny/read-only ruleHigh 8.6 13 Aug 2026
- CVE-2026-70462rsync: Peer-supplied MSG_IO_TIMEOUT defeats the client's own I/O timeout (signed overflow, and a non-positive value)High 7.1 13 Aug 2026
- CVE-2026-70461rsync: Peer-driven one-byte heap out-of-bounds write in add_implied_include()High 8.8 13 Aug 2026
- CVE-2026-70460rsync: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-module symlinkCritical 9.2 13 Aug 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-53795
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-53795
- GitHub Advisory Database https://github.com/advisories/GHSA-m9vj-637x-v6pq
- github.com https://github.com/RsyncProject/rsync/security/advisories/GHSA-m9vj-637x-v6pq