Sender service interrupt via zero-length checksum block
Published Aug 13, 2026 · Updated Aug 13, 2026
Out-of-bounds read in rsync before 3.5.0 allows remote attackers controlling a receiver to interrupt a sender via a zero-length checksum block. When a checksum header reports a positive block count and a zero block length, sender-side rolling-match arithmetic computes a negative offset and reads before the file-data buffer. Exploitation requires the sender to initiate a transfer with the malicious receiver; the published impact is confined to sender availability, with no reported data disclosure or modification.
Summary
What happened
Out-of-bounds read in rsync before 3.5.0 allows remote attackers controlling a receiver to interrupt a sender via a zero-length checksum block. When a checksum header reports a positive block count and a zero block length, sender-side rolling-match arithmetic computes a negative offset and reads before the file-data buffer. Exploitation requires the sender to initiate a transfer with the malicious receiver; the published impact is confined to sender availability, with no reported data disclosure or modification.
The record
- CVE
- CVE-2026-53792
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Rsync Project
- Product
- rsync
- Classifications
- CWE-787, CWE-129, 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=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.
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