CVE-2026-44508
Rsync receiver memory disclosure via compressed-token overflow (fixed in 3.4.3)
Is CVE-2026-44508 being exploited?
Not confirmed. CVE-2026-44508 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-44508?
CVE-2026-44508 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44508?
Yes. A fix has been recorded for CVE-2026-44508. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44508 affect?
CVE-2026-44508 affects rsync < 3.4.3, rsync receiver/daemon, Linux/Unix systems running rsync receivers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44508?
Upgrade receivers to rsync 3.4.3; restrict untrusted senders; monitor rsync logs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote sender can trigger overflow on rsync receiver to read process memory, leaking env vars, passwords and pointers and aiding ASLR bypass and follow-on exploits.
Patch when possible