Authorization bypass via failed reverse DNS lookup
Published May 20, 2026 · Updated May 20, 2026
Authorization bypass in the rsync daemon before 3.4.3 allows remote attackers to evade hostname deny rules after reverse DNS failure. The daemon calls client_name() after entering the global daemon chroot; failed name resolution stores UNKNOWN, causing allow_access() hostname patterns to miss. Exposure requires a daemon chroot without resolver support and hostname-based deny rules; affected clients can reach modules intended to reject them.
Summary
What happened
Authorization bypass in the rsync daemon before 3.4.3 allows remote attackers to evade hostname deny rules after reverse DNS failure. The daemon calls client_name() after entering the global daemon chroot; failed name resolution stores UNKNOWN, causing allow_access() hostname patterns to miss. Exposure requires a daemon chroot without resolver support and hostname-based deny rules; affected clients can reach modules intended to reject them.
The record
- CVE
- CVE-2026-43617
- Published
- May 20, 2026
- Updated
- May 20, 2026
- Vendor
- Rsync Project
- Product
- rsync
- Classifications
- CWE-289, CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2026CVE publishedPublication date reported by the CVE source.
- May 20, 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.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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