Rsync is widely deployed for backups and file sync across enterprises; arbitrary file write can lead to widespread compromise and service disruption.
CVE-2026-70460
Rsync path traversal via symlinks allows arbitrary file writes with --partial-dir/--backup-dir.
Is CVE-2026-70460 being exploited?
Not confirmed. CVE-2026-70460 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.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-70460?
CVE-2026-70460 is rated Critical with a CVSS score of 9.2. 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-70460?
Yes. A fix has been recorded for CVE-2026-70460. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70460 affect?
CVE-2026-70460 affects rsync < 3.5.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70460?
Upgrade to rsync 3.5.0+, restrict module write access and untrusted senders.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker with write access to an rsync module can escape the module root via symlinks and write arbitrary files outside it, enabling config overwrite, backdoors, or privilege escalation.
Immediate action required
- affected>= 2.3.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.