Daemon heap corruption via full argument allocation
Published Aug 13, 2026 · Updated Aug 13, 2026
Out-of-bounds write in rsync 3.0.1 through 3.4.4 allows remote attackers to corrupt heap memory through a crafted daemon request. In read_args(), glob expansion can make argc equal maxargs, and the code then stores the trailing NULL pointer one slot beyond the argv allocation. A remote daemon client must hit the exact argument boundary; the overwrite threatens the connection worker's availability and processing integrity, with no reported data disclosure.
Summary
What happened
Out-of-bounds write in rsync 3.0.1 through 3.4.4 allows remote attackers to corrupt heap memory through a crafted daemon request. In read_args(), glob expansion can make argc equal maxargs, and the code then stores the trailing NULL pointer one slot beyond the argv allocation. A remote daemon client must hit the exact argument boundary; the overwrite threatens the connection worker's availability and processing integrity, with no reported data disclosure.
The record
- CVE
- CVE-2026-70456
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Rsync Project
- Product
- rsync
- Classifications
- CWE-787, T1190
- 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.1 <=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