Skip to content
Applications

CVE-2026-53784

8.4
High
EPSS 0.24%Patch availableAug 14, 2026

Rsync daemon path traversal allows remote access to files outside module root.

common questions

Is CVE-2026-53784 being exploited?

Not confirmed. CVE-2026-53784 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.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-53784?

CVE-2026-53784 is rated High with a CVSS score of 8.4. 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-53784?

Yes. A fix has been recorded for CVE-2026-53784. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-53784 affect?

CVE-2026-53784 affects rsync daemon < 3.5.0, Unix/Linux systems running rsync in daemon mode, Systems with module root as a symlink and chroot disabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-53784?

Upgrade to rsync 3.5.0+, enable chroot or avoid symlinked module roots.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
rsync daemon < 3.5.0Unix/Linux systems running rsync in daemon modeSystems with module root as a symlink and chroot disabled
impact

Remote attackers can read files outside the intended module root via path traversal when daemon chroot is disabled and module root is a symlink.

action required

Patch when possible

affected versions
RsyncProject rsync
  • affected<= 3.4.4
vendor says fixed in3.5.0

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free