rsync before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to write files outside the intended destination directory tree by crafting relative paths with symlink components in --relative mode. The make_path() function follows symlinks pointing outside the destination tree while creating intermediate directories without verifying that created paths remain within the destination boundary, enabling arbitrary file writes on the receiver's filesystem.
CVE-2026-53785
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% 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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
September 8, 2026
Advisory Details (3)
Auto-updated Aug 13, 2026rsync < 3.5.0 Path Traversal Write Escape via --relative Mode | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rsync-path-traversal-write-escape-via-relative-modev3.5.0
Patch available: RsyncProject/rsync v3.5.0
https://github.com/RsyncProject/rsync/releases/tag/v3.5.0rsync: --relative implied-parent creation escapes the destination tree · Advisory · RsyncProject/rsync · GitHub
Affected: 3.5.0. (Precise introduced-in ranges being finalised.)
https://github.com/RsyncProject/rsync/security/advisories/GHSA-pph3-7xmf-rrqgVendor Advisories for CVE-2026-53785(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rsync-0:3.5.0-3.el10_2 | 2026-09-14 | redhat |
| redhat | rsync-0:3.2.7-1.el9_8 | 2026-09-14 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(7 across 7 ecosystems)
Alpine:v3.21(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rsync | — | 3.5.0-r0 | — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rsync | — | 3.5.0-r0 | — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rsync | — | 3.5.0-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rsync | — | 3.5.0-r0 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rsync | 3.2.7-1 ... 3.5.0+ds1-2 (30 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rsync | 3.4.1+ds1-5 ... 3.5.0+ds1-2 (15 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rsync | 3.4.1+ds1-5 ... 3.4.4+ds1-1 (9 versions) | 3.5.0+ds1-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 18× in last 7d / 57× 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-09-19 03:34 UTCEG score recompute
- 2026-09-19 03:34 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 14:49 UTCVendor advisory
- 2026-09-18 02:04 UTCEG score recompute
- 2026-09-18 02:04 UTCVendor advisory
- 2026-09-17 13:19 UTCVendor advisory
- 2026-09-17 00:00 UTCEG score recompute
- 2026-09-17 00:00 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 11:12 UTCEG score recompute
- 2026-09-16 11:12 UTCVendor advisory
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 22:28 UTCVendor advisory
- 2026-09-15 09:34 UTCEG score recompute
- 2026-09-13 19:15 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 17:46 UTCEG score recompute
- 2026-09-11 16:17 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 14:27 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 09:41 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 20:57 UTCEG score recompute
Show 48 moreShow fewer
- 2026-09-07 19:25 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 17:31 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 16:01 UTCEG score recompute
- 2026-09-04 14:09 UTCEG score recompute
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 23:11 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 01:57 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 13:11 UTCEG score recompute
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 21:57 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 09:12 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 07:41 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 00:49 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 23:16 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 21:46 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 20:09 UTCEG score recompute
- 2026-08-23 05:54 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 04:19 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 02:49 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 00:35 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 23:05 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 21:36 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 20:07 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:22 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 05:53 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 13:14 UTCEG score recompute
- 2026-08-13 15:24 UTCEG score recompute
- 2026-08-13 15:13 UTCEG score recompute
- 2026-08-13 15:11 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-53785?
When was CVE-2026-53785 disclosed?
Is CVE-2026-53785 actively exploited?
What is the CVSS score of CVE-2026-53785?
How do I remediate CVE-2026-53785?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53785
Is Your Infrastructure Affected by CVE-2026-53785?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.