CVE-2026-70456
rsync heap out-of-bounds write via crafted sender arguments
Is CVE-2026-70456 being exploited?
Not confirmed. CVE-2026-70456 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. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-70456?
CVE-2026-70456 is rated High with a CVSS score of 8.8. 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-70456?
Yes. A fix has been recorded for CVE-2026-70456. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70456 affect?
CVE-2026-70456 affects rsync < 3.5.0, Unix/Linux servers, Backup servers, CI/CD systems using rsync. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70456?
Upgrade rsync to >=3.5.0 and restrict/monitor rsync access
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A malicious rsync sender can send a crafted argument list to corrupt heap memory, causing crashes and potentially enabling remote code execution.
Patch when possible
- affected>= 3.0.1 and <= 3.4.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.