Process-memory disclosure via signed counter overflow
Published Jul 20, 2026 · Updated Jul 20, 2026
Integer overflow in rsync before 3.4.3 allows remote authenticated users acting as senders to read receiver process memory. The compressed-token decoder adds token lengths to a 32-bit signed counter without checking for overflow, causing reads beyond the intended buffer. Exploitation requires a compressed transfer to the receiver and exposes heap, stack, library, environment, password, and pointer data.
Summary
What happened
Integer overflow in rsync before 3.4.3 allows remote authenticated users acting as senders to read receiver process memory. The compressed-token decoder adds token lengths to a 32-bit signed counter without checking for overflow, causing reads beyond the intended buffer. Exploitation requires a compressed transfer to the receiver and exposes heap, stack, library, environment, password, and pointer data.
The record
- CVE
- CVE-2026-44508
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- Rsync Project
- Product
- rsync
- Classifications
- CWE-190, CWE-200, T1190
- Attack vector
- network
- Privileges
- authenticated
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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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