CVE-2026-53789

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.4% (27th percentile of EPSS-scored CVEs). 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, nvd
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

rsync before 3.5.0 contains an improper path handling vulnerability that allows a malicious sender to expand the scope of --delete operations beyond the intended destination subtree by sending a crafted file list that causes rsync to reclassify implied parent directory entries or treat synthetic paths as the transfer root. Attackers can exploit multiple variants including implied parent reclassification, synthetic root path construction, legacy protocol behavior below version 30, and non-directory root handling to cause the receiver to delete files outside the authorized destination directory.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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.5.0 Arbitrary File Deletion via Malicious File List | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rsync-arbitrary-file-deletion-via-malicious-file-list
github_release Patch Available

v3.5.0

Patch available: RsyncProject/rsync v3.5.0

https://github.com/RsyncProject/rsync/releases/tag/v3.5.0
githubMentions a patch (unverified)

rsync: malicious sender expands --delete scope by reclassifying an implied parent · Advisory · RsyncProject/rsync · GitHub

Affected: 3.5.0. (Precise introduced-in ranges being finalised.)

https://github.com/RsyncProject/rsync/security/advisories/GHSA-fxwg-7hmf-xh5q

Vendor Advisories for CVE-2026-53789(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrsync-0:3.1.3-28.el8_102026-09-30redhat
redhatrhcos-4.22.9.8.202609221802-02026-09-29redhat
redhatrsync-0:3.5.0-3.el10_22026-09-14redhat
redhatrsync-0:3.2.7-1.el9_82026-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 rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
rsync—
  • every version up to 3.5.0-r0: fixed in 3.5.0-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.2.7-1 ... 3.5.1+ds1-1 (32 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5 ... 3.4.4+ds1-1 (13 versions)
  • every version up to 3.5.0+ds1-0+deb13u1: fixed in 3.5.0+ds1-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rsync3.4.1+ds1-5 ... 3.4.4+ds1-1 (9 versions)
  • every version up to 3.5.0+ds1-1: fixed in 3.5.0+ds1-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

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 / 78× 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 131 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53789?
CVE-2026-53789 is a high vulnerability published on August 13, 2026. rsync before 3.5.0 contains an improper path handling vulnerability that allows a malicious sender to expand the scope of --delete operations beyond the intended destination subtree by sending a crafted file list that causes rsync to reclassify implied parent directory entries or treat synthetic…
When was CVE-2026-53789 disclosed?
CVE-2026-53789 was first published 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-53789 actively exploited?
CVE-2026-53789 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53789?
CVE-2026-53789 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-53789?
A fix for CVE-2026-53789 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53789 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53789?

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

Book a Demo →Browse All CVEs