rsync daemon 2.0.0 before 3.5.0 contains a denial of service vulnerability that allows unauthenticated remote attackers to exhaust daemon connection slots by stalling the handshake process before or after module selection without triggering the I/O timeout. Attackers can open many simultaneous connections and trickle data at the minimum rate to avoid timeout, or stall entirely before module selection where no timeout applies, consuming all available connection slots and denying service to legitimate clients.
CVE-2026-70464
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 54% 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.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/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 computedSeverity75% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 46%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
September 8, 2026
Advisory Details (3)
Auto-updated Aug 13, 2026rsync 2.0.0 < 3.5.0 Connection Slot Exhaustion DoS via Handshake Stall | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rsync-connection-slot-exhaustion-dos-via-handshake-stallv3.5.0
Patch available: RsyncProject/rsync v3.5.0
https://github.com/RsyncProject/rsync/releases/tag/v3.5.0rsync: Unauthenticated pre-transfer handshake DoS locks out an rsync daemon module · Advisory · RsyncProject/rsync · GitHub
https://github.com/RsyncProject/rsync/security/advisories/GHSA-hrwq-ccf7-rw5mVendor Advisories for CVE-2026-70464(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
(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 / 98× 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 119 total refreshes for this CVE.
- 2026-09-18 22:52 UTCEG score recompute
- 2026-09-18 22:52 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 11:40 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:00 UTCEG score recompute
- 2026-09-17 00:00 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 10:32 UTCEG score recompute
- 2026-09-16 10:32 UTCVendor advisory
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 21:55 UTCVendor advisory
- 2026-09-15 09:44 UTCEG score recompute
- 2026-09-15 09:44 UTCVendor advisory
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 22:33 UTCVendor advisory
- 2026-09-14 11:22 UTCVendor advisory
- 2026-09-14 00:11 UTCEG score recompute
- 2026-09-14 00:11 UTCVendor advisory
- 2026-09-13 13:00 UTCVendor advisory
- 2026-09-13 01:49 UTCEG score recompute
- 2026-09-13 01:49 UTCVendor advisory
- 2026-09-12 15:02 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-12 14:38 UTCVendor advisory
- 2026-09-12 03:28 UTCVendor advisory
- 2026-09-11 16:17 UTCEG score recompute
- 2026-09-11 16:17 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 17:41 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 19:18 UTCVendor advisory
- 2026-09-09 08:07 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 20:57 UTCEG score recompute
- 2026-09-08 03:44 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 21:41 UTCEG score recompute
- 2026-09-06 21:41 UTCVendor advisory
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 10:23 UTCVendor advisory
- 2026-09-05 23:13 UTCEG score recompute
- 2026-09-05 23:13 UTCVendor advisory
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 12:02 UTCVendor advisory
- 2026-09-05 00:32 UTCEG score recompute
- 2026-09-05 00:32 UTCVendor advisory
- 2026-09-04 10:25 UTCEG score recompute
- 2026-09-04 10:25 UTCVendor advisory
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 23:13 UTCVendor advisory
- 2026-09-03 11:21 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:33 UTCEG score recompute
- 2026-09-01 22:33 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 06:00 UTCEG score recompute
- 2026-08-31 06:00 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 18:49 UTCVendor advisory
- 2026-08-30 07:38 UTCEG score recompute
- 2026-08-30 07:38 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:27 UTCVendor advisory
- 2026-08-29 07:41 UTCEG score recompute
- 2026-08-29 07:41 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:23 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:57 UTCVendor advisory
- 2026-08-25 21:46 UTCEG score recompute
- 2026-08-25 21:46 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 10:24 UTCVendor advisory
- 2026-08-24 23:13 UTCEG score recompute
- 2026-08-24 23:13 UTCVendor advisory
- 2026-08-24 12:02 UTCEG score recompute
- 2026-08-24 12:02 UTCVendor advisory
- 2026-08-23 02:29 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 04:07 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 05:45 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 20:12 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
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-770
Frequently asked(5)
What is CVE-2026-70464?
When was CVE-2026-70464 disclosed?
Is CVE-2026-70464 actively exploited?
What is the CVSS score of CVE-2026-70464?
How do I remediate CVE-2026-70464?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70464
Is Your Infrastructure Affected by CVE-2026-70464?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.