# CVE-2026-44510: Rsync out-of-bounds read in recv_files

Source: https://junglewise.ai/threats/cve-2026-44510-rsync-out-of-bounds-read-in-recv-files  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-20. Updated: 2026-07-20  
License: CC BY 4.0 with a link back

CVE-2026-44510 · Severity: medium · CVSS 6.5 · Published 2026-07-20

Rsync is a widely used tool for synchronizing and copying files between computers. A vulnerability in the client-side software allows a malicious server to crash the rsync client during a file transfer. While this issue can disrupt operations and cause service outages, it is currently assessed as a crash-only bug that does not allow for data theft or unauthorized system access.

Technologies: [RsyncProject Rsync](https://junglewise.ai/threats/technologies/rsync). Vendors: [RsyncProject](https://junglewise.ai/threats/vendors/rsyncproject).

## Quick answers

**Is CVE-2026-44510 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-44510 being exploited in the wild.

**How severe is CVE-2026-44510?** Medium severity, with a CVSS score of 6.5, published 20 July 2026.

**Which products and versions are affected?** RsyncProject Rsync < 3.4.3.

**Is there a fix for CVE-2026-44510?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-44510 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-44510?** Check whether you run RsyncProject Rsync at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An out-of-bounds (OOB) array read exists in the recv_files() function in rsync versions prior to 3.4.3. By manipulating the wire-protocol-level communication, a malicious sender can set the 'parent_ndx' to -1 and send a specific transfer record that bypasses existing checks. This causes the receiver to read 8 bytes before the allocated pointer array and dereference the resulting value, leading to a segmentation fault (SEGV). The vulnerability affects clients performing recursive pulls (the default behavior in protocol 30+) and can be mitigated by using the --no-inc-recursive flag or upgrading to version 3.4.3. Analysis indicates the OOB read typically lands in unmapped memory metadata, making it a crash-only vulnerability.

## Affected products

- RsyncProject rsync < 3.4.3

## Timeline

- 2026-05-20: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: CVE published to NVD

## References

- [https://github.com/RsyncProject/rsync/security/advisories/GHSA-28pw-r563-rxvm](https://github.com/RsyncProject/rsync/security/advisories/GHSA-28pw-r563-rxvm)

## Related threats

- [rsync denial of service in hash_search()](https://junglewise.ai/threats/cve-2026-119741-rsync-through-3-5-1-contains-a-denial-of-service-vulnerability)
- [RsyncProject rsync symlink race in path-based syscalls](https://junglewise.ai/threats/cve-2026-44509-rsyncproject-rsync-symlink-race-in-path-based-syscalls)
- [Rsync integer overflow in compressed-token decoder](https://junglewise.ai/threats/cve-2026-44508-rsync-integer-overflow-in-compressed-token-decoder)
- [Rsync hostname ACL bypass in chroot daemon mode](https://junglewise.ai/threats/cve-2026-44507-rsync-hostname-acl-bypass-in-chroot-daemon-mode)
- [Rsync TOCTOU race condition in daemon file handling](https://junglewise.ai/threats/cve-2026-29518-rsync-toctou-race-condition-in-daemon-file-handling)