External risk intelligence

Rsync Path Traversal via Symlinks in Partial or Backup Directories

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-70460

Rsync is frequently deployed across networks. While often used in controlled environments, it is commonly exposed publicly for synchronization tasks. The vulnerability requires a specific configuration involving symlinks and untrusted senders, making exposure plausible but dependent on the specific implementation.

Path Traversal

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A path traversal vulnerability has been identified in rsync, a tool used for file synchronization. This issue allows a malicious sender to write files to arbitrary locations outside the intended directory by exploiting symbolic links, potentially impacting system security if not properly managed. The primary concern is to confirm if this technology is in use and if it is exposed to untrusted inputs.

  • Malicious symlinks can overwrite files anywhere.
  • Its widespread use makes it a critical risk.
  • Confirm if this sync tool is exposed to untrusted input.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by placing a symbolic link within a configured rsync module directory. This symlink, when combined with specific rsync options, allows the attacker to trick the rsync process into writing files to arbitrary locations on the server, potentially overwriting critical system files or gaining unauthorized access.

  • Attacker must place a symlink.
  • Vulnerability triggered by specific rsync options.
  • Results in arbitrary file write outside module.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a malicious sender could exploit rsync's handling of symlinks within partial or backup directories to write files to arbitrary locations outside the intended module root. This could affect system data or service behavior.

  • Arbitrary file write access.
  • Exploits symlinks in module root.
  • Compromises system integrity.

Operational Fix

Recommended remediation, mitigation, and detection steps

The rsync vulnerability impacts systems where it's used for synchronization, potentially affecting application owners, infrastructure teams, and security operations. The first step is to identify all rsync deployments, confirm exposure and criticality, and then map them to their accountable owners to prioritize remediation.

  • Identify affected rsync instances and owners.
  • Verify vulnerable configurations and exposure.
  • Plan remediation during approved maintenance.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is rsync used for?

Rsync is a widely used command-line utility for efficient file synchronization and transfer between local and remote systems. It is commonly utilized for backups, mirroring directory structures, and keeping files consistent across different servers or storage locations.

What does CVE-2026-70460 mean by path traversal?

This vulnerability, classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) and CWE-59 (Improper Link Resolution), allows an attacker to bypass directory restrictions. By leveraging symlinks, an attacker can trick the software into writing files outside of the intended, restricted folder, potentially allowing them to modify or overwrite files elsewhere on the system.

How is this rsync vulnerability triggered?

The flaw requires two conditions: the use of specific options, namely --partial-dir or --backup-dir, and the presence of a symlink that the sender can influence or exploit. Standard rsync operations that do not utilize these specific directory options or involve untrusted input within the module file tree are not subject to this specific path traversal behavior.

Do I need to worry if my rsync instance is internal?

Halo Surface Signal indicates that while rsync is frequently deployed in controlled environments, it is often exposed publicly for synchronization tasks. You should evaluate if your specific instance accepts input from untrusted sources, as the vulnerability relies on a malicious sender's ability to interact with the module root.

What are the first steps to address CVE-2026-70460?

Begin by auditing your environment to locate all active rsync deployments and confirm which versions are in use. Once identified, verify if those instances are configured with the vulnerable --partial-dir or --backup-dir options. Finally, coordinate with system owners to prioritize updating to rsync version 3.5.0 or later to eliminate the risk.

References