rsync Daemon PROXY Protocol IP Spoofing Access Control Bypass

Technical Analysis

CVE-2026-53791 (CVSS 9.1) affects rsync daemon implementations that support the PROXY protocol for identifying originating client addresses behind load balancers or proxies. Because the daemon trusts the client-supplied PROXY header without validating it against the actual TCP connection source, an attacker can forge the header to impersonate an allow-listed IP and bypass hosts allow/deny rules enforced in rsyncd.conf. This is a pre-authentication bypass requiring only direct network reachability to the rsync daemon port (typically 873), making it highly exploitable in environments relying on IP allow-listing as a primary control. Many CI/CD pipelines, model artifact repositories, and dataset synchronization jobs used by AI/ML and agent infrastructure rely on rsync daemons for pulling training data, model weights, or configuration files, and organizations running AI agents that use rsync-based sync jobs to pull models, embeddings, or RAG corpora could have their access controls bypassed, exposing sensitive data or allowing injection of poisoned artifacts into agent pipelines.

Affected Systems

rsync daemon (rsyncd) versions prior to 3.5.0 configured with hosts allow/deny access controls and PROXY protocol support enabled; Linux/Unix servers exposing rsync daemon on TCP port 873 (or configured alternate ports), including NAS devices, mirror servers, backup infrastructure, and CI/CD artifact repositories.

Indicators of Compromise

• N/A - vulnerability disclosure, no known IOCs published at this time
• Monitor for anomalous PROXY protocol headers in rsync daemon connection logs
• Unexpected rsync daemon access from IPs not matching PROXY header claimed source

Remediation Steps

1. 1

   Upgrade rsync

   Update rsync daemon to version 3.5.0 or later where the PROXY protocol header validation issue is fixed.

2. 2

   Disable PROXY protocol support

   If not strictly required, disable PROXY protocol parsing in rsyncd.conf to eliminate the spoofing vector.

3. 3

   Enforce network segmentation

   Restrict direct network access to the rsync daemon port using firewalls or VPNs rather than relying solely on IP-based application-layer allow-listing.

4. 4

   Add authentication controls

   Require rsync daemon authentication (secrets file/module passwords) in addition to IP-based restrictions to reduce reliance on spoofable IP checks.

5. 5

   Audit access logs

   Review rsync daemon logs for unexpected access patterns or PROXY header usage, especially from artifact repositories feeding AI/ML training or RAG pipelines.