Client crash via receiver array under-read
Published May 20, 2026 · Updated May 20, 2026
Out-of-bounds read in rsync before 3.4.3 allows remote attackers controlling a sending peer to crash a client during a recursive pull. recv_files() uses ndx=0 after a crafted incremental file list leaves parent_ndx at -1, reading eight bytes before the file-pointer array and dereferencing an invalid pointer. A normal protocol-30-or-later recursive pull needs no special client options; exploitation ends the client process with SIGSEGV without reported data disclosure or modification.
Summary
What happened
Out-of-bounds read in rsync before 3.4.3 allows remote attackers controlling a sending peer to crash a client during a recursive pull. recv_files() uses ndx=0 after a crafted incremental file list leaves parent_ndx at -1, reading eight bytes before the file-pointer array and dereferencing an invalid pointer. A normal protocol-30-or-later recursive pull needs no special client options; exploitation ends the client process with SIGSEGV without reported data disclosure or modification.
The record
- CVE
- CVE-2026-43620
- Published
- May 20, 2026
- Updated
- May 20, 2026
- Vendor
- Rsync Project
- Product
- rsync
- Classifications
- CWE-125, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2026CVE publishedPublication date reported by the CVE source.
- May 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.4.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo