rsync before 3.5.0 contains a symlink race condition vulnerability in the --remove-source-files feature that allows attackers with symlink creation access to cause arbitrary file deletion. Attackers can atomically substitute a symlink for a source file between transfer completion and the unlink() call, causing rsync to delete the symlink target rather than the intended source file.
CVE-2026-53800
This medium-severity CVE scores 4.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% 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
- 4.7
- EG Score
- 4.7(medium)
- EG Risk
- 21(Track)EG Risk 21/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 computedSeverity47% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- 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 via --remove-source-files | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rsync-symlink-race-condition-via-remove-source-filesrsync: --remove-source-files unlink follows a parent-component symlink race -> file deletion outside the source tree · Advisory · RsyncProject/rsync · GitHub
Affected: 3.5.0. (Precise introduced-in ranges being finalised.)
https://github.com/RsyncProject/rsync/security/advisories/GHSA-v3vw-pvpg-chwhv3.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 11× in last 7d / 33× 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:41 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 16:27 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 14:15 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 10:00 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 07:54 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 05:47 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 03:41 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 01:34 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 23:28 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 21:20 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 19:14 UTCEG score recompute
Show 8 moreShow fewer
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:07 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-53800?
When was CVE-2026-53800 disclosed?
Is CVE-2026-53800 actively exploited?
What is the CVSS score of CVE-2026-53800?
How do I remediate CVE-2026-53800?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-53800
Is Your Infrastructure Affected by CVE-2026-53800?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.