rsync before 3.5.0 contains a path traversal vulnerability that allows remote clients to access files outside the intended module root when use chroot is disabled and the module root path or a component of it is a symlink. The daemon calls chdir() to the module root at session initialization without resolving symlinks via realpath() or equivalent, causing subsequent relative-path operations to reference files relative to the symlink target rather than the intended module root, enabling unauthorized file access.
CVE-2026-53784
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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
- 15%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 31, 2026
Advisory Details (3)
Auto-updated Aug 13, 2026rsync < 3.5.0 Path Traversal via Symlink Module Root | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rsync-path-traversal-via-symlink-module-rootv3.5.0
Patch available: RsyncProject/rsync v3.5.0
https://github.com/RsyncProject/rsync/releases/tag/v3.5.0rsync: daemon module-root chdir escape under "use chroot = no" · Advisory · RsyncProject/rsync · GitHub
Affected: 3.5.0. (Precise introduced-in ranges being finalised.)
https://github.com/RsyncProject/rsync/security/advisories/GHSA-ffg2-fr5g-3rxwVendor Advisories for CVE-2026-53784(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 17× in last 7d / 56× 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:17 UTCEG score recompute
- 2026-09-19 03:17 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 14:38 UTCVendor advisory
- 2026-09-18 01:58 UTCEG score recompute
- 2026-09-18 01:58 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 05:15 UTCEPSS rescore
- 2026-09-16 01:43 UTCVendor advisory
- 2026-09-15 13:04 UTCEG score recompute
- 2026-09-15 13:04 UTCVendor advisory
- 2026-09-13 22:58 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 21:40 UTCEG score recompute
- 2026-09-11 20:22 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 19:02 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 04:58 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 18:24 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
Show 48 moreShow fewer
- 2026-09-06 16:58 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 15:39 UTCEG score recompute
- 2026-09-05 02:49 UTCEG score recompute
- 2026-09-04 13:59 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-01 18:57 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 06:16 UTCEG score recompute
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 21:50 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 09:11 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 07:43 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 19:56 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-25 18:32 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 17:15 UTCEG score recompute
- 2026-08-23 02:13 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 00:55 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 23:36 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 22:18 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:58 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 19:35 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 18:17 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:37 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 04:20 UTCEG score recompute
- 2026-08-15 03:23 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
Frequently asked(5)
What is CVE-2026-53784?
When was CVE-2026-53784 disclosed?
Is CVE-2026-53784 actively exploited?
What is the CVSS score of CVE-2026-53784?
How do I remediate CVE-2026-53784?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53784
Is Your Infrastructure Affected by CVE-2026-53784?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.