Skip to content
Noroxi
CVE-2026-53789· NVD / CVE Program· CNA VulnCheck

rsync < 3.5.0 Arbitrary File Deletion via Malicious File List

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.

HighCVSS 7.1 · v4.0—No exploit Fix available
Published
Aug 13, 2026
Updated
Aug 31, 2026
EPSS
0.5% · 43th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · VulnCheck
7.1
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
sambarsync

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • samba rsyncbefore 3.5.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.

  • RsyncProject rsync

    • 3.5.0not affected
    • up to and including 3.4.4affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10rsyncbefore 3.5.0-3.el10_23.5.0-3.el10_2
AlmaLinux:10rsync-daemonbefore 3.5.0-3.el10_23.5.0-3.el10_2
AlmaLinux:10rsync-rrsyncbefore 3.5.0-3.el10_23.5.0-3.el10_2
AlmaLinux:9rsyncbefore 3.2.7-1.el9_83.2.7-1.el9_8
AlmaLinux:9rsync-daemonbefore 3.2.7-1.el9_83.2.7-1.el9_8
AlmaLinux:9rsync-rrsyncbefore 3.2.7-1.el9_83.2.7-1.el9_8
Alpine:v3.21rsyncbefore 3.5.0-r03.5.0-r0
Debian:12rsyncall versions—
Debian:13rsyncbefore 3.5.0+ds1-0+deb13u13.5.0+ds1-0+deb13u1
Debian:14rsyncbefore 3.5.0+ds1-13.5.0+ds1-1
openSUSE:Leap 16.0rsyncbefore 3.4.1-160000.6.13.4.1-160000.6.1
openSUSE:Tumbleweedrsyncbefore 3.5.1-1.13.5.1-1.1
Red Hat:enterprise_linux:10.2rsyncbefore 0:3.5.0-3.el10_20:3.5.0-3.el10_2
Red Hat:enterprise_linux:10.2rsync-daemonbefore 0:3.5.0-3.el10_20:3.5.0-3.el10_2
Red Hat:enterprise_linux:10.2rsync-debuginfobefore 0:3.5.0-3.el10_20:3.5.0-3.el10_2
Red Hat:enterprise_linux:10.2rsync-debugsourcebefore 0:3.5.0-3.el10_20:3.5.0-3.el10_2
Red Hat:enterprise_linux:10.2rsync-rrsyncbefore 0:3.5.0-3.el10_20:3.5.0-3.el10_2
Red Hat:enterprise_linux:9::appstreamrsync-daemonbefore 0:3.2.7-1.el9_80:3.2.7-1.el9_8
Red Hat:enterprise_linux:9::appstreamrsync-rrsyncbefore 0:3.2.7-1.el9_80:3.2.7-1.el9_8
Red Hat:enterprise_linux:9::baseosrsyncbefore 0:3.2.7-1.el9_80:3.2.7-1.el9_8
Red Hat:enterprise_linux:9::baseosrsync-debuginfobefore 0:3.2.7-1.el9_80:3.2.7-1.el9_8
Red Hat:enterprise_linux:9::baseosrsync-debugsourcebefore 0:3.2.7-1.el9_80:3.2.7-1.el9_8
Rocky Linux:10rsyncbefore 0:3.5.0-3.el10_20:3.5.0-3.el10_2
Rocky Linux:9rsyncbefore 0:3.2.7-1.el9_80:3.2.7-1.el9_8

+5

Other highest-scoring records for the same primary product.

  • CVE-2024-12084Rsync: heap buffer overflow in rsync due to improper checksum length handling
    61This week
  • CVE-2017-16548The receive_xattr function in xattrs.c in rsync 3.1.2 and 3.1.3-development does not check for a trailing '\0' character in an xattr name, w
    41Plan
  • CVE-2017-17434The daemon in rsync 3.1.2, and 3.1.3-development before 2017-12-03, does not check for fnamecmp filenames in the daemon_filter_list data str
    40Plan
  • CVE-2017-15994rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to bypass intended access
    39Monitor
  • CVE-2026-53791rsync < 3.5.0 Daemon IP Spoofing via PROXY Protocol Header
    36Monitor
  • CVE-2026-70461rsync 3.2.5 < 3.5.0 Heap Out-of-Bounds Write via files-from Entry
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:rsync3.2.7-1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:rsync-daemon3.2.7-1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:rsync-rrsync3.2.7-1.el9_8 · AlmaLinux:9Package registry (OSV)
alpine:rsync3.5.0-r0 · Alpine:v3.21Package registry (OSV)
debian:rsync3.5.0+ds1-0+deb13u1 · Debian:13Package registry (OSV)
opensuse:rsync3.5.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:rsync0:3.2.7-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:rsync-daemon0:3.2.7-1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:rsync-debuginfo0:3.2.7-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:rsync-debugsource0:3.2.7-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:rsync-rrsync0:3.2.7-1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:rsync0:3.2.7-1.el9_8 · Rocky Linux:9Package registry (OSV)
suse:rsync3.2.7-8.1 · SUSE:Linux Micro 6.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
P
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records