Remote memory corruption via invalid hard-link flag
Published Aug 13, 2026 · Updated Aug 13, 2026
Out-of-bounds write in rsync 3.0.0 through 3.4.4 allows remote attackers to corrupt receiver memory via crafted file entries. The receiver accepts FLAG_HLINKED without negotiated hard-link preservation, so F_SUM addresses attacker-supplied bytes beyond the allocated file entry. Exploitation requires protocol-30 incremental recursion, a regular file, checksum mode, and no -H, and the write can corrupt adjacent memory or crash the receiver.
Summary
What happened
Out-of-bounds write in rsync 3.0.0 through 3.4.4 allows remote attackers to corrupt receiver memory via crafted file entries. The receiver accepts FLAG_HLINKED without negotiated hard-link preservation, so F_SUM addresses attacker-supplied bytes beyond the allocated file entry. Exploitation requires protocol-30 incremental recursion, a regular file, checksum mode, and no -H, and the write can corrupt adjacent memory or crash the receiver.
The record
- CVE
- CVE-2026-70458
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Rsync Project
- Product
- rsync
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 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.0.0 <=3.4.4
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.
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