CVE-2026-41035: In rsync 3.0.1 through 3.4.1, receive_xattr relies on an untrusted length value during a qsort call, leadin...
In rsync 3.0.1 through 3.4.1, receive_xattr relies on an untrusted length value during a qsort call, leading to a receiver use-after-free. The victim must run rsync with -X (aka --xattrs). On Linux, many (but not all) common configurations are vulnerable. Non-Linux platforms are more widely vulnerable.
Security readout for executives and security teams
Plain-English summary
A malicious or compromised rsync peer may corrupt memory when the receiving system preserves extended attributes. Successful exploitation could disrupt service or affect data and confidentiality. The flaw applies to rsync 3.0.1 through 3.4.1, but actual exposure depends on platform and configuration.
Executive priority
High priority for internet-accessible, partner-facing, or multi-tenant receivers using extended attributes. Inventory immediately and remediate promptly. Systems without -X or --xattrs are outside the stated trigger condition, but owners should verify actual runtime arguments rather than relying solely on package presence.
Technical view
receive_xattr trusts an attacker-influenced length during qsort, causing a receiver use-after-free. Triggering requires the victim to run rsync with -X or --xattrs. The CVSS 3.1 score is 7.4: network-reachable, low complexity, low privileges, no user interaction, changed scope, and low impact across confidentiality, integrity, and availability.
Likely exposure
Prioritize systems running rsync 3.0.1 through 3.4.1 that receive data from untrusted or lower-trust peers with extended-attribute preservation enabled. Many, but not all, common Linux configurations are vulnerable. The supplied description says non-Linux platforms are more widely vulnerable; configuration-specific coverage is incomplete.
Exploitation context
The CVSS vector indicates network attackability with low privileges and no user interaction. CISA KEV status is false, and the supplied sources do not establish active exploitation or a publicly weaponized exploit. Treat exposed receivers as credible targets without claiming exploitation in the wild.
Researcher notes
CWE-130 and CWE-805 describe improper length handling and incorrect buffer access. Platform susceptibility is not uniform, so version-only scanning will overstate exposure. Validation should combine package version, receiver role, runtime flags, trust boundary, platform, and vendor package status. The bundle does not provide crash indicators, a definitive fixed upstream version, or proof of code execution.
Mitigation direction
Apply the applicable rsync or operating-system vendor security update after compatibility testing.
Consult rsync releases and distribution advisories for the correct fixed package; no fixed version is supplied.
Temporarily disable -X or --xattrs where extended-attribute preservation is unnecessary.
Restrict rsync access to trusted, authenticated peers and networks while remediation is pending.
Validation and detection
Inventory installed rsync versions and identify systems within 3.0.1 through 3.4.1.
Review jobs, services, wrappers, and automation for -X or --xattrs usage.
Identify receivers accepting connections or data from untrusted or lower-trust accounts.
Confirm the installed package matches the applicable vendor advisory after updating.
Retest required synchronization workflows, including extended attributes, after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-130: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-130 · source CWE mapping
Improper Handling of Length Parameter Inconsistency
Improper Handling of Length Parameter Inconsistency represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Buffer Access with Incorrect Length Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.