rsync 2.3.3 < 3.5.0 Path Traversal via --partial-dir/--backup-dir Symlink
RsyncProject · rsync
9.2CriticalCVSS 4.0
Recommended action
Within 72 hours
Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
Patch available
Distribution package intelligence
Ubuntu vendor package status
Canonical’s release and source-package findings are shown separately from local repository availability.
1 package state
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
Ubuntu release
Source package
Vendor state
Fixed version
Evidence
Ubuntu 24.04 LTSnoble · standard archive
rsync
Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
rsync as a component of Red Hat Enterprise Linux 10
rsync-daemon as a component of Red Hat Enterprise Linux 10
rsync-rrsync as a component of Red Hat Enterprise Linux 10
rsync.src as a component of Red Hat Enterprise Linux 10
rsync as a component of Red Hat Enterprise Linux 6
rsync.src as a component of Red Hat Enterprise Linux 6
rsync as a component of Red Hat Enterprise Linux 7
rsync.src as a component of Red Hat Enterprise Linux 7
rsync as a component of Red Hat Enterprise Linux 8
rsync-daemon as a component of Red Hat Enterprise Linux 8
rsync.src as a component of Red Hat Enterprise Linux 8
rsync as a component of Red Hat Enterprise Linux 9
Summary
A path traversal and symlink vulnerability in rsync allows a malicious sender with write access to write files outside the intended directory. By exploiting symbolic links in conjunction with the --partial-dir or --backup-dir options, an attacker can bypass path restrictions to modify arbitrary system files, compromising system integrity
Remediation
Disable the rsyncd daemon if it is unused (systemctl disable --now rsyncd), or strictly limit TCP/873 access to trusted clients via firewall rules. Within rsyncd.conf, block the exploit vectors directly by setting refuse options = partial-dir backup-dir and maintain defense-in-depth by enforcing use chroot = yes. Finally, ensure no root- or daemon-owned symlinks point outside your module paths, and avoid using the vulnerable flags when operating as a client against untrusted sources.
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-58044
No EUVD known-exploited evidence
ENISA has published the identifier mapping but no EUVD description has been stored yet.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours
Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
Patch available
01
What, why and how
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.
What
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.
Why
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.None recorded
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
Likely attack path
a network path → Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Not a CVSS 4.0 base metric
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-22
A
Official authority intelligence
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2026-58044Official EUVD mapping
0 linked advisory records.
Official EUVD recordBSI · German · WID-SEC-W-2026-2817Rsync: Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in Rsync ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, Daten offenzulegen oder zu manipulieren, Sicherheitsmaßnahmen zu umgehen oder Denial-of-Service-Zustände herbeizuführen.
Official advisoryCSIRT Italia · Italian · rilevate-vulnerabilita-in-rsync-1Rilevate vulnerabilità in Rsync
Rilevate 19 vulnerabilità, di cui 5 con gravità “critica” e 14 con gravità "alta", in Rsync, software open source per la sincronizzazione e il trasferimento di file tra sistemi.
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 6; rsync.src as a component of Red Hat Enterprise Linux 6; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Fixed
3.5.0
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
Disable the rsyncd daemon if it is unused (systemctl disable --now rsyncd), or strictly limit TCP/873 access to trusted clients via firewall rules. Within rsyncd.conf, block the exploit vectors directly by setting refuse options = partial-dir backup-dir and maintain defense-in-depth by enforcing use chroot = yes. Finally, ensure no root- or daemon-owned symlinks point outside your module paths, and avoid using the vulnerable flags when operating as a client against untrusted sources.
04
Evidence and provenance
Published 13 Aug 2026 · Last source change 14 Aug 2026, 16:51 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-58044
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 6; rsync.src as a component of Red Hat Enterprise Linux 6; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
After
rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 6; rsync.src as a component of Red Hat Enterprise Linux 6; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Affected versionsThe structured affected or fixed version information changed.
Before
rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 6; rsync.src as a component of Red Hat Enterprise Linux 6; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; rhcos as a component of Red Hat OpenShift Container Platform 4
After
rsync as a component of Red Hat Enterprise Linux 10; rsync-daemon as a component of Red Hat Enterprise Linux 10; rsync-rrsync as a component of Red Hat Enterprise Linux 10; rsync.src as a component of Red Hat Enterprise Linux 10; rsync as a component of Red Hat Enterprise Linux 6; rsync.src as a component of Red Hat Enterprise Linux 6; rsync as a component of Red Hat Enterprise Linux 7; rsync.src as a component of Red Hat Enterprise Linux 7; rsync as a component of Red Hat Enterprise Linux 8; rsync-daemon as a component of Red Hat Enterprise Linux 8; rsync.src as a component of Red Hat Enterprise Linux 8; rsync as a component of Red Hat Enterprise Linux 9; rsync-daemon as a component of Red Hat Enterprise Linux 9; rsync-rrsync as a component of Red Hat Enterprise Linux 9; rsync.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
