rsync 2.3.3 before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to escape the module root by exploiting symlinks within the module file tree when using --partial-dir or --backup-dir options. Attackers with write access to place a symlink under the module root, or who can exploit a pre-existing trusted symlink, can direct file writes to locations outside the intended module root, achieving arbitrary file write relative to the module root parent.
CVE-2026-70460
This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 62% 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
- 8.1
- EG Score
- 8.1(medium)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 38%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
September 8, 2026
Advisory Details (3)
Auto-updated Aug 13, 2026rsync 2.3.3 < 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rsync-path-traversal-via-partial-dir-backup-dir-symlinkv3.5.0
Patch available: RsyncProject/rsync v3.5.0
https://github.com/RsyncProject/rsync/releases/tag/v3.5.0rsync: Daemon module-root escape through a peer-supplied --partial-dir / --backup-dir resolving via an in-module symlink · Advisory · RsyncProject/rsync · GitHub
https://github.com/RsyncProject/rsync/security/advisories/GHSA-w3xf-j2r2-gv4xVendor Advisories for CVE-2026-70460(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(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
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 26× in last 7d / 97× 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.
Showing the most recent 100 of 118 total refreshes for this CVE.
- 2026-09-19 00:23 UTCEG score recompute
- 2026-09-19 00:23 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 12:50 UTCVendor advisory
- 2026-09-18 00:29 UTCEG score recompute
- 2026-09-18 00:29 UTCVendor advisory
- 2026-09-17 12:04 UTCVendor advisory
- 2026-09-17 00:13 UTCEG score recompute
- 2026-09-17 00:13 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 12:40 UTCEG score recompute
- 2026-09-16 12:40 UTCVendor advisory
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 01:07 UTCVendor advisory
- 2026-09-15 12:10 UTCEG score recompute
- 2026-09-15 12:10 UTCVendor advisory
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 22:32 UTCVendor advisory
- 2026-09-14 10:59 UTCVendor advisory
- 2026-09-13 23:26 UTCEG score recompute
- 2026-09-13 23:26 UTCVendor advisory
- 2026-09-13 11:54 UTCVendor advisory
- 2026-09-13 00:21 UTCEG score recompute
- 2026-09-13 00:21 UTCVendor advisory
- 2026-09-12 15:02 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-12 12:48 UTCVendor advisory
- 2026-09-12 01:15 UTCEG score recompute
- 2026-09-12 01:15 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 13:42 UTCEG score recompute
- 2026-09-10 13:10 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 08:30 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 20:57 UTCEG score recompute
- 2026-09-08 04:07 UTCVendor advisory
- 2026-09-07 16:33 UTCEG score recompute
- 2026-09-07 16:33 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 23:29 UTCEG score recompute
- 2026-09-06 23:29 UTCVendor advisory
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 11:56 UTCVendor advisory
- 2026-09-06 00:24 UTCEG score recompute
- 2026-09-06 00:24 UTCVendor advisory
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 12:51 UTCVendor advisory
- 2026-09-05 00:32 UTCEG score recompute
- 2026-09-05 00:32 UTCVendor advisory
- 2026-09-04 11:11 UTCEG score recompute
- 2026-09-04 11:11 UTCVendor advisory
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 23:13 UTCVendor advisory
- 2026-09-03 11:17 UTCVendor advisory
- 2026-09-02 23:11 UTCEG score recompute
- 2026-09-02 23:11 UTCVendor advisory
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 22:54 UTCEG score recompute
- 2026-09-01 22:54 UTCVendor advisory
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 11:21 UTCEG score recompute
- 2026-09-01 11:21 UTCVendor advisory
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 21:34 UTCVendor advisory
- 2026-08-31 07:05 UTCVendor advisory
- 2026-08-30 19:32 UTCEG score recompute
- 2026-08-30 19:32 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 08:00 UTCEG score recompute
- 2026-08-30 08:00 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:27 UTCVendor advisory
- 2026-08-29 07:40 UTCEG score recompute
- 2026-08-29 07:40 UTCVendor advisory
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 07:09 UTCVendor advisory
- 2026-08-27 19:33 UTCEG score recompute
- 2026-08-27 19:33 UTCVendor advisory
- 2026-08-27 07:45 UTCVendor advisory
- 2026-08-26 20:12 UTCEG score recompute
- 2026-08-26 20:12 UTCVendor advisory
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 08:38 UTCVendor advisory
- 2026-08-25 21:04 UTCEG score recompute
- 2026-08-25 21:04 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 09:31 UTCVendor advisory
- 2026-08-24 21:58 UTCEG score recompute
- 2026-08-24 21:58 UTCVendor advisory
- 2026-08-24 10:26 UTCEG score recompute
- 2026-08-24 10:26 UTCVendor advisory
- 2026-08-23 11:21 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 00:43 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 01:36 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 02:09 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 15:03 UTCEG score recompute
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- 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
- CVE-2001-0011EG 10.0EPSS p94HIGH
- CVE-2001-0013EG 10.0EPSS p96HIGH
Same CWE
10 shownCWE-22 · CWE-59
Frequently asked(5)
What is CVE-2026-70460?
When was CVE-2026-70460 disclosed?
Is CVE-2026-70460 actively exploited?
What is the CVSS score of CVE-2026-70460?
How do I remediate CVE-2026-70460?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70460
Is Your Infrastructure Affected by CVE-2026-70460?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.