Quick answers
- Is CVE-2026-44508 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44508 being exploited in the wild.
- How severe is CVE-2026-44508?
- High severity, with a CVSS score of 8.1, published 20 July 2026.
- Which products and versions are affected?
- RsyncProject Rsync < 3.4.3.
- Is there a fix for CVE-2026-44508?
- 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-44508 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44508?
- 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 integer overflow vulnerability (CWE-190) exists in the rsync receiver's compressed-token decoder. The component fails to check for overflow when accumulating a 32-bit signed counter. A malicious sender can exploit this by sending specially crafted compressed data to trigger the overflow, leading to an out-of-bounds read. This allows the extraction of sensitive data from the process memory, including environment variables, passwords, and stack/heap pointers. The leakage of these pointers can be used to bypass Address Space Layout Randomization (ASLR), facilitating further exploitation. The issue is fixed in version 3.4.3; a workaround involves disabling compression in rsyncd.conf.
Affected products
- RsyncProject rsync < 3.4.3
Timeline
- 2026-05-20: advisory: Initial GitHub advisory published
- 2026-07-20: disclosed: NVD publication date