CVE-2026-70455

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

rsync 3.4.2 before 3.5.0 contains a denial of service vulnerability that allows a remote sender to exhaust system resources by specifying the --zt short alias for --compress-threads, which bypasses the refuse options directive's string matching on long option names. Attackers can specify --zt=N with a large value to spawn an unbounded number of Zstandard worker threads on the receiver, exhausting available thread and memory resources.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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 computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 31, 2026

Advisory Details (3)

Auto-updated Aug 13, 2026
Patch available. Sources: github, github_release.
generic

rsync 3.4.2 < 3.5.0 DoS via --zt Zstandard Compression Thread Exhaustion | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-dos-via-zt-zstandard-compression-thread-exhaustion
github_release Patch Available

v3.5.0

Patch available: RsyncProject/rsync v3.5.0

https://github.com/RsyncProject/rsync/releases/tag/v3.5.0
github Patch Available

rsync: Peer-controlled Zstandard worker exhaustion on an rsync daemon · Advisory · RsyncProject/rsync · GitHub

https://github.com/RsyncProject/rsync/security/advisories/GHSA-rjvj-qgqg-cvx9

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrsync-0:3.5.0-3.el10_22026-09-14redhat

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)
PackageVulnerable rangeFixed inDependents
rsync—3.5.0-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
rsync—3.5.0-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
rsync—3.5.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
rsync—3.5.0-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rsync3.2.7-1 ... 3.5.0+ds1-2 (30 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rsync3.4.1+ds1-5 ... 3.5.0+ds1-2 (15 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rsync3.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.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 26× in last 7d / 94× 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 116 total refreshes for this CVE.

  1. 2026-09-21 00:09 UTCEG score recompute
  2. 2026-09-21 00:09 UTCVendor advisory
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 10:09 UTCVendor advisory
  5. 2026-09-19 19:40 UTCEG score recompute
  6. 2026-09-19 19:40 UTCVendor advisory
  7. 2026-09-19 05:58 UTCEG score recompute
  8. 2026-09-19 05:58 UTCVendor advisory
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 16:53 UTCVendor advisory
  11. 2026-09-18 02:23 UTCEG score recompute
  12. 2026-09-18 02:23 UTCVendor advisory
  13. 2026-09-17 13:19 UTCVendor advisory
  14. 2026-09-17 00:00 UTCEG score recompute
  15. 2026-09-17 00:00 UTCVendor advisory
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 10:30 UTCEG score recompute
  18. 2026-09-16 10:30 UTCVendor advisory
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-15 20:08 UTCVendor advisory
  21. 2026-09-15 06:20 UTCEG score recompute
  22. 2026-09-15 06:20 UTCVendor advisory
  23. 2026-09-15 03:12 UTCEPSS rescore
  24. 2026-09-14 17:16 UTCVendor advisory
  25. 2026-09-14 04:12 UTCEG score recompute
Show 75 more
  1. 2026-09-14 04:12 UTCVendor advisory
  2. 2026-09-13 15:09 UTCVendor advisory
  3. 2026-09-13 02:03 UTCEG score recompute
  4. 2026-09-13 02:03 UTCVendor advisory
  5. 2026-09-12 15:02 UTCEPSS rescore
  6. 2026-09-12 12:59 UTCVendor advisory
  7. 2026-09-11 23:55 UTCEG score recompute
  8. 2026-09-11 23:55 UTCVendor advisory
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-10 20:09 UTCEG score recompute
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-09 18:01 UTCVendor advisory
  13. 2026-09-09 04:58 UTCEG score recompute
  14. 2026-09-09 04:58 UTCVendor advisory
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-08 06:19 UTCVendor advisory
  17. 2026-09-07 16:32 UTCEG score recompute
  18. 2026-09-07 16:32 UTCVendor advisory
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 19:57 UTCEG score recompute
  21. 2026-09-06 19:57 UTCVendor advisory
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-05 17:31 UTCEG score recompute
  24. 2026-09-05 17:31 UTCVendor advisory
  25. 2026-09-05 15:31 UTCEPSS rescore
  26. 2026-09-05 03:56 UTCVendor advisory
  27. 2026-09-04 14:52 UTCEG score recompute
  28. 2026-09-04 14:52 UTCVendor advisory
  29. 2026-09-04 05:07 UTCEPSS rescore
  30. 2026-09-04 01:40 UTCVendor advisory
  31. 2026-09-03 12:36 UTCVendor advisory
  32. 2026-09-02 23:11 UTCEG score recompute
  33. 2026-09-02 23:11 UTCVendor advisory
  34. 2026-09-02 14:12 UTCEPSS rescore
  35. 2026-09-01 20:18 UTCEG score recompute
  36. 2026-09-01 20:18 UTCVendor advisory
  37. 2026-09-01 13:54 UTCEPSS rescore
  38. 2026-09-01 06:16 UTCEG score recompute
  39. 2026-09-01 06:16 UTCVendor advisory
  40. 2026-09-01 04:40 UTCEPSS rescore
  41. 2026-08-31 15:36 UTCVendor advisory
  42. 2026-08-31 12:05 UTCVendor advisory
  43. 2026-08-30 22:57 UTCEG score recompute
  44. 2026-08-30 22:57 UTCVendor advisory
  45. 2026-08-30 19:17 UTCEPSS rescore
  46. 2026-08-30 09:54 UTCEG score recompute
  47. 2026-08-30 09:54 UTCVendor advisory
  48. 2026-08-30 01:22 UTCEPSS rescore
  49. 2026-08-29 20:45 UTCVendor advisory
  50. 2026-08-29 07:40 UTCEG score recompute
  51. 2026-08-29 07:40 UTCVendor advisory
  52. 2026-08-28 21:42 UTCEPSS rescore
  53. 2026-08-28 10:10 UTCVendor advisory
  54. 2026-08-27 20:38 UTCEG score recompute
  55. 2026-08-27 20:38 UTCVendor advisory
  56. 2026-08-27 07:17 UTCVendor advisory
  57. 2026-08-26 17:26 UTCEG score recompute
  58. 2026-08-26 17:26 UTCVendor advisory
  59. 2026-08-26 14:47 UTCEPSS rescore
  60. 2026-08-26 08:26 UTCVendor advisory
  61. 2026-08-25 19:23 UTCEG score recompute
  62. 2026-08-25 19:23 UTCVendor advisory
  63. 2026-08-25 13:49 UTCEPSS rescore
  64. 2026-08-25 06:18 UTCVendor advisory
  65. 2026-08-24 17:15 UTCEG score recompute
  66. 2026-08-24 17:15 UTCVendor advisory
  67. 2026-08-23 00:51 UTCEG score recompute
  68. 2026-08-23 00:19 UTCEPSS rescore
  69. 2026-08-22 11:47 UTCEG score recompute
  70. 2026-08-21 23:49 UTCEPSS rescore
  71. 2026-08-21 09:39 UTCEG score recompute
  72. 2026-08-20 22:56 UTCEPSS rescore
  73. 2026-08-19 18:28 UTCEG score recompute
  74. 2026-08-19 17:04 UTCEPSS rescore
  75. 2026-08-18 15:43 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-70455?
CVE-2026-70455 is a high vulnerability published on August 13, 2026. rsync 3.4.2 before 3.5.0 contains a denial of service vulnerability that allows a remote sender to exhaust system resources by specifying the --zt short alias for --compress-threads, which bypasses the refuse options directive's string matching on long option names. Attackers can specify --zt=N…
When was CVE-2026-70455 disclosed?
CVE-2026-70455 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70455 actively exploited?
CVE-2026-70455 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.3% of all scored CVEs.
What is the CVSS score of CVE-2026-70455?
CVE-2026-70455 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-70455?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70455, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70455

Explore →

Is Your Infrastructure Affected by CVE-2026-70455?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs