Receiver crash via incorrect xattr sort count
Published Apr 16, 2026 · Updated Sep 1, 2026
Use-after-free in rsync 3.0.1 through 3.4.1 allows remote authenticated users to crash a receiver via crafted xattrs. receive_xattr passes the wire-supplied entry count to qsort after filtering entries, so the comparator processes stale or uninitialized array elements. Reaching the bug requires --xattrs; Linux receivers additionally need --fake-super or a qualifying xattr filter, while maintainers dispute security impact beyond terminating the sender's connection.
Summary
What happened
Use-after-free in rsync 3.0.1 through 3.4.1 allows remote authenticated users to crash a receiver via crafted xattrs. receive_xattr passes the wire-supplied entry count to qsort after filtering entries, so the comparator processes stale or uninitialized array elements. Reaching the bug requires --xattrs; Linux receivers additionally need --fake-super or a qualifying xattr filter, while maintainers dispute security impact beyond terminating the sender's connection.
The record
- CVE
- CVE-2026-41035
- Published
- Apr 16, 2026
- Updated
- Sep 1, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift Container Platform 4.16
- Classifications
- CWE-130, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 1, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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