CVE-2026-70457
rsync OOB write in parse_size_arg allowing crash or potential RCE
Is CVE-2026-70457 being exploited?
Not confirmed. CVE-2026-70457 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.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-70457?
CVE-2026-70457 is rated High with a CVSS score of 8.3. 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-70457?
Yes. A fix has been recorded for CVE-2026-70457. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70457 affect?
CVE-2026-70457 affects rsync < 3.5.0 (e.g., 3.2.3), Servers running rsync daemon/clients, Backup & file-sync appliances using rsync. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70457?
Upgrade to rsync 3.5.0+ and restrict/monitor rsync access
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Out-of-bounds write in parse_size_arg can corrupt .bss, causing crashes (DoS) or enabling remote code execution via crafted size strings.
Patch when possible
- affected>= 3.2.3 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.