Servers and applications
CVE-2026-70461
rsync: Peer-driven one-byte heap out-of-bounds write in add_implied_include()
- Severity
- High 8.8
- Published
- 13 Aug 2026
- Last changed
- 24 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.5.0
- Exploit chance
- 0.6% in the next 30 daysHigher than 47% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Out-of-bounds write (CWE-787)
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Change some data · Take it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/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-jhxm-j4mq-3fj4
- Sources
- NVD, Project advisories (GitHub)
Description
add_implied_include() builds an implied "/**" filter rule from each transfer argument the client sends, so the remote sender can validate the file list against it. It under-counted a trailing backslash when sizing the buffer for that rule, so the rule was written one byte past a heap allocation. The value that overflows is supplied by the peer.
Demonstrated against a standard network rsync --daemon with a READ-ONLY module: a remote, unauthenticated client sends -r --files-from= with a files-from entry carrying both an interior and a trailing backslash (a\b), and forward_filesfrom_data() feeds it to add_implied_include() on the daemon side. The per-module parse_arguments() runs with am_server == 0, so trust_sender_args stays 0 and the implied-include path is active.
A read-only module is enough; no write access and no crafted protocol are needed. The write is one byte and its content is constrained, so code execution is not claimed; heap corruption is, and the regression detects it…
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-70460rsync: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-module symlinkCritical 9.2 13 Aug 2026
- CVE-2026-70459rsync: Per-connection daemon child crash from a crafted first incremental file list with a non-directory transfer rootMedium 6.9 13 Aug 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-70461
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-70461
- GitHub Advisory Database https://github.com/advisories/GHSA-jhxm-j4mq-3fj4
- github.com https://github.com/RsyncProject/rsync/security/advisories/GHSA-jhxm-j4mq-3fj4