Servers and applications
CVE-2026-45232
rsync: off-by-one stack OOB write in HTTP CONNECT proxy response parsing
- Severity
- Low 2.1
- Published
- 20 May 2026
- Last changed
- 24 Jul 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.4.3
- Exploit chance
- 0.3% in the next 30 daysHigher than 27% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Only under certain conditions · No login needed · Needs someone to click or open something
- Attacker can
- Slow it down
- CVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:L/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-8f85-j2cv-59m8
- Sources
- NVD, Project advisories (GitHub)
Description
The rsync client's HTTP CONNECT proxy support contains an off-by-one out-of-bounds stack write in establish_proxy_connection() (socket.c). After issuing the CONNECT request, rsync reads the proxy's first response line one byte at a time into a 1024-byte stack buffer with the bound cp < &buffer[sizeof buffer - 1], so the loop only ever writes buffer[0..sizeof-2]. If the proxy (or a man-in-the-middle in front of it) returns 1023+ bytes on the first response line without a '\n' terminator, the loop exits with cp == &buffer[sizeof buffer - 1] — a slot the loop never wrote, so *cp holds stale stack bytes left there by the earlier snprintf() that formatted the outgoing CONNECT request. The post-loop code then does:
The '\0' lands one byte past the end of the on-stack buffer[1024], corrupting whatever lives in the adjacent stack slot. AddressSanitizer reports stack-buffer-overflow at socket.c:95 in the establish_proxy_connection frame.
Workarounds
- Do not set RSYNC_PROXY, or only use trusted HTTP proxies on trusted networks, until you have upgraded to 3.4.3.
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-45232
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-45232
- GitHub Advisory Database https://github.com/advisories/GHSA-8f85-j2cv-59m8
- github.com https://github.com/RsyncProject/rsync/security/advisories/GHSA-8f85-j2cv-59m8