Skip to main content
Mallory
HighVulnerability

CVE-2026-53802: Arbitrary File Read via Symlink Following in rsync

Published Aug 13, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days9 mentions · peak 2 in a dayToday
CVSS8.4High · v4
EPSS0.24%15th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Samba
IdentifiersCVE-2026-53802CWE-59

CVE-2026-53802 is an arbitrary file read vulnerability in rsync versions before 3.5.0. Improper symlink following during input configuration handling affects --files-from, --password-file, and filter merge files. Attackers can redirect input-file reads by placing symlinks at predictable input locations or supplying a --files-from path that escapes the daemon module root. Successful exploitation exposes files readable by the rsync daemon process, including files outside the intended module subtree.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Attackers can obtain unauthorized access to file contents within the rsync daemon process's filesystem permissions, potentially disclosing sensitive information outside the configured module root. The scope of disclosure depends on the daemon's privileges and filesystem access. Arbitrary file writes, code execution, and service disruption are not established by the vulnerability's described mechanism.

Mitigation

If you can’t patch tonight, do this now.

Pending patching, restrict untrusted users' ability to create or replace symlinks at input-file locations and prevent attacker-controlled input paths from being used by rsync. Keep input configuration files and their parent directories under trusted ownership and minimize the daemon account's filesystem read permissions. These measures reduce exposure but are not established substitutes for the security update.

Remediation

Patch, then assume compromise.

Upgrade rsync to version 3.5.0 or later, or install a distribution security update that backports the fix. Update rsync-daemon where packaged separately. Identified fixed packages include rsync 3.5.0-1.ph5 for Photon OS 5.0 and rsync 3.5.0+ds1-0+deb13u1 for Debian trixie.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SambaRsyncapplication
FAQ

Frequently asked questions

Is CVE-2026-53802 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-53802 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-53802?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-53802.
Is there a patch for CVE-2026-53802?
Upgrade rsync to version 3.5.0 or later, or install a distribution security update that backports the fix. Update rsync-daemon where packaged separately.
What products are affected by CVE-2026-53802?
Samba Rsync.
How severe is CVE-2026-53802?
CVE-2026-53802 has a CVSS v4 score of 8.4 (High) and an EPSS score of 0.24% (15th percentile) as of Nov 17, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.