IP-based access-control bypass via untrusted PROXY headers
Published Aug 13, 2026 · Updated Aug 13, 2026
Authentication bypass in rsync daemon before 3.5.0 allows remote attackers to evade IP-based access controls using forged PROXY headers. The daemon trusts the header's forwarded source address without verifying that the direct peer is an authorized proxy, then evaluates hosts allow/deny against the forged address. Exposure requires the non-default proxy protocol setting, a directly reachable daemon port, and IP-based module restrictions; successful spoofing grants access those rules should block.
Summary
What happened
Authentication bypass in rsync daemon before 3.5.0 allows remote attackers to evade IP-based access controls using forged PROXY headers. The daemon trusts the header's forwarded source address without verifying that the direct peer is an authorized proxy, then evaluates hosts allow/deny against the forged address. Exposure requires the non-default proxy protocol setting, a directly reachable daemon port, and IP-based module restrictions; successful spoofing grants access those rules should block.
The record
- CVE
- CVE-2026-53791
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Rsync Project
- Product
- rsync
- Classifications
- CWE-290, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.4.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo