Client crash via negative receiver array index
Published Jul 20, 2026 · Updated Jul 20, 2026
Out-of-bounds read in rsync before 3.4.3 allows remote attackers controlling a sender to crash a client during a recursive pull. recv_files() uses a negative parent_ndx from a crafted incremental file list to index before dir_flist->files, then passes the invalid pointer to f_name(). A client must initiate the pull; glibc x86-64 Linux crashes deterministically, while other allocators remain unaudited, and this CVE identifier is rejected as a duplicate of CVE-2026-43620.
Summary
What happened
Out-of-bounds read in rsync before 3.4.3 allows remote attackers controlling a sender to crash a client during a recursive pull. recv_files() uses a negative parent_ndx from a crafted incremental file list to index before dir_flist->files, then passes the invalid pointer to f_name(). A client must initiate the pull; glibc x86-64 Linux crashes deterministically, while other allocators remain unaudited, and this CVE identifier is rejected as a duplicate of CVE-2026-43620.
The record
- CVE
- CVE-2026-44510
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- Rsync Project
- Product
- rsync
- Classifications
- CWE-125, CAPEC-540, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 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=< 3.4.3
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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