rsync is widely deployed across server infrastructure; a memory-corruption flaw can impact many systems and enable crashes or code execution.
CVE-2026-70458
Out‑of‑bounds write in rsync allows memory corruption, crashes, or potential code execution.
Is CVE-2026-70458 being exploited?
Not confirmed. CVE-2026-70458 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-70458?
CVE-2026-70458 is rated High. 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-70458?
Yes. A fix has been recorded for CVE-2026-70458. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70458 affect?
CVE-2026-70458 affects rsync < 3.5.0, rsync daemon, rsync client (network transfers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70458?
Upgrade to rsync 3.5.0+ now; restrict rsync access and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malformed rsync file entries trigger out‑of‑bounds writes, corrupting heap/stack, causing crashes or enabling remote code execution via rsync transfers.
Immediate action required
- affected>= 3.0.0 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.