CVE-2026-53801
Rsync sender symlink race can expose files outside the module root.
Is CVE-2026-53801 being exploited?
Not confirmed. CVE-2026-53801 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-53801?
CVE-2026-53801 is rated High with a CVSS score of 8.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-53801?
Yes. A fix has been recorded for CVE-2026-53801. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53801 affect?
CVE-2026-53801 affects rsync < 3.5.0 (sender-side), daemon-mode sender, non-daemon sender, Unix/Linux systems running rsync. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53801?
Upgrade sender-side rsync to 3.5.0+; restrict symlink creation and audit senders.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Race condition lets attacker-controlled symlinks force sender to enumerate and transfer files outside module root, causing unauthorized file disclosure/exfiltration.
Patch when possible
- affected<= 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.