Skip to main content
Mallory
HighVulnerability

CVE-2026-53803: Local Privilege Escalation via Symlink Following in rsync

Published Aug 13, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS8.5High · v4
EPSS0.23%14th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Samba
IdentifiersCVE-2026-53803CWE-59 · Improper Link Resolution Before…

CVE-2026-53803 is a symlink-following vulnerability in rsync versions before 3.5.0. rsync fails to reject symbolic links when writing ancillary output, including logging, batch output, and daemon-mode log and statistics data. A local attacker who can place a symlink at a predictable output location can redirect these writes to arbitrary filesystem targets accessible to the rsync process. When rsync runs with elevated privileges, this can enable local privilege escalation.

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.

Successful exploitation can overwrite or corrupt files with the permissions of the rsync process, compromising filesystem integrity and potentially disrupting services. On setuid installations or privileged daemon configurations, modification of security-sensitive files can enable local privilege escalation, with potentially high confidentiality, integrity, and availability impacts. The scope of accessible targets depends on the process privileges and filesystem restrictions.

Mitigation

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

Until patched, restrict ancillary output to directories that untrusted local users cannot modify, including their parent directories. Avoid running rsync with unnecessary elevated privileges and remove unnecessary setuid deployment configurations. These measures reduce exposure; no vendor-provided temporary workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade rsync to version 3.5.0 or later, or install a distribution security update that addresses CVE-2026-53803. Debian stable (trixie) provides the fix in 3.5.0+ds1-0+deb13u1; Photon OS provides rsync 3.5.0-1.ph5. Update associated rsync-daemon packages where applicable.

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-53803 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-53803 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-53803?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-53803.
Is there a patch for CVE-2026-53803?
Upgrade rsync to version 3.5.0 or later, or install a distribution security update that addresses CVE-2026-53803. Debian stable (trixie) provides the fix in 3.5.0+ds1-0+deb13u1; Photon OS provides rsync 3.5.0-1.ph5.
What products are affected by CVE-2026-53803?
Samba Rsync.
How severe is CVE-2026-53803?
CVE-2026-53803 has a CVSS v4 score of 8.5 (High) and an EPSS score of 0.23% (14th percentile) as of Nov 14, 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 activity3Community discussion across Reddit, Mastodon, and other social sources.