rsync before 3.5.0 contains a symlink race condition vulnerability in the sender's directory scanning logic that allows attackers to cause the sender to enumerate and transfer files outside the module root's intended subtree. Attackers who can create or manipulate symlinks in a path component of the scanned tree can replace a symlink with a directory entry pointing outside the module root between the lstat() call and the subsequent opendir() call, exposing files beyond the intended root in both daemon-mode and non-daemon sender-side scanning.
CVE-2026-53801
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 26, 2026
Advisory Details (3)
Auto-updated Aug 13, 2026rsync < 3.5.0 Symlink Race Condition Directory Traversal | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rsync-symlink-race-condition-directory-traversalrsync: sender/daemon directory-scan enumeration escapes the transfer root/module -> out-of-tree disclosure · Advisory · RsyncProject/rsync · GitHub
Affected: 3.5.0. (Precise introduced-in ranges being finalised.)
https://github.com/RsyncProject/rsync/security/advisories/GHSA-mch3-qr4p-chgmv3.5.0
Patch available: RsyncProject/rsync v3.5.0
https://github.com/RsyncProject/rsync/releases/tag/v3.5.0Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 34× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 07:40 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 19:33 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:26 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 09:59 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 08:28 UTCEG score recompute
- 2026-08-23 05:26 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 03:56 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 02:25 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 00:53 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 23:18 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 21:46 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 20:10 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
Show 9 moreShow fewer
- 2026-08-15 18:39 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:08 UTCEG score recompute
- 2026-08-14 16:32 UTCEG score recompute
- 2026-08-14 16:04 UTCEG score recompute
- 2026-08-14 13:14 UTCEG score recompute
- 2026-08-13 15:23 UTCEG score recompute
- 2026-08-13 15:12 UTCEG score recompute
- 2026-08-13 15:11 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-53801?
When was CVE-2026-53801 disclosed?
Is CVE-2026-53801 actively exploited?
What is the CVSS score of CVE-2026-53801?
How do I remediate CVE-2026-53801?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-53801
Is Your Infrastructure Affected by CVE-2026-53801?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.