{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-44507", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-05-06T18:28:20.886Z", "datePublished": "2026-07-20T20:29:26.577Z", "dateUpdated": "2026-07-20T20:29:26.577Z"}, "containers": {"cna": {"title": "Rsync: hostname/ACL bypass on DNS-lookup failure", "problemTypes": [{"descriptions": [{"cweId": "CWE-863", "lang": "en", "description": "CWE-863: Incorrect Authorization", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.8, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N", "version": "3.1"}}], "references": [{"name": "https://github.com/RsyncProject/rsync/security/advisories/GHSA-rjfm-3w2m-jf4f", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/RsyncProject/rsync/security/advisories/GHSA-rjfm-3w2m-jf4f"}], "affected": [{"vendor": "RsyncProject", "product": "rsync", "versions": [{"version": "< 3.4.3", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-07-20T20:29:26.577Z"}, "descriptions": [{"lang": "en", "value": "Rsync is a file-copying tool that uses a delta-transfer algorithm to synchronize remote and local files. In versions prior to 3.4.3, when using a daemon configured with a chroot, the reverse DNS lookup of the connecting client was performed after the chroot had been entered. If the chroot did not contain the files glibc needs for resolution (/etc/resolv.conf, /etc/nsswitch.conf,\n/etc/hosts, NSS service modules), the lookup failed and the connecting hostname was set to \"UNKNOWN\". Hostname-based deny rules (\"hosts deny = *.evil.example\") therefore could not match, and an attacker who controlled the PTR record for their source IP could connect from a hostname that the administrator had intended to deny. IP-based ACLs (\"hosts allow = 10.0.0.0/8\") are unaffected. This issue is fixed in version 3.4.3."}], "source": {"advisory": "GHSA-rjfm-3w2m-jf4f", "discovery": "UNKNOWN"}}}}

{}

{}

{}

{}