Skip to main content
Mallory
HighVulnerability

CVE-2026-53783: Directory Restriction Bypass in rsync rrsync via TOCTOU Race

Published Aug 13, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 1 in a dayToday
CVSS8.6High · v4
EPSS0.43%38th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Samba
IdentifiersCVE-2026-53783CWE-367

A time-of-check to time-of-use (TOCTOU) race condition in the rrsync restricted shell wrapper in rsync before 3.5.0 allows authenticated clients to escape enforced directory restrictions. An attacker can replace a path component with a symbolic link after path validation but before transfer processing, redirecting file operations outside the permitted directory subtree. Unrestricted options, including --copy-unsafe-links, -D, and --log-file, can additionally enable reads or writes outside that 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.

Successful exploitation compromises the confidentiality and integrity of files outside the directory subtree enforced by rrsync, subject to the filesystem permissions of the executing account. Authenticated clients can obtain unauthorized file contents or write files beyond their intended access boundary. The vulnerability-specific assessments identify high confidentiality and integrity impacts and no direct availability impact.

Mitigation

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

No vulnerability-specific temporary workaround is documented. Apply the relevant security update rather than relying on rrsync directory restrictions alone.

Remediation

Patch, then assume compromise.

Upgrade rsync and its rrsync wrapper to version 3.5.0 or later, or install distribution security updates that backport the fix. For Debian stable (trixie), upgrade rsync to 3.5.0+ds1-0+deb13u1 or a later security-updated version. Update any separately packaged rrsync component used to enforce restricted access.

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-53783 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-53783 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-53783?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-53783.
Is there a patch for CVE-2026-53783?
Upgrade rsync and its rrsync wrapper to version 3.5.0 or later, or install distribution security updates that backport the fix. For Debian stable (trixie), upgrade rsync to 3.5.0+ds1-0+deb13u1 or a later security-updated version.
What products are affected by CVE-2026-53783?
Samba Rsync.
How severe is CVE-2026-53783?
CVE-2026-53783 has a CVSS v4 score of 8.6 (High) and an EPSS score of 0.43% (38th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+25 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 activity1Community discussion across Reddit, Mastodon, and other social sources.