CVE-2026-41035: CWE-130 Improper Handling of Length Parameter Inconsistency in Samba rsync
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.
AI Analysis
Technical Summary
This vulnerability in rsync (versions 3.0.1 through 3.4.1) arises from improper handling of an untrusted length value during a qsort call in the receive_xattr function, leading to a use-after-free condition. Exploitation requires the victim to run rsync with the -X option to handle extended attributes. The vulnerability affects many Linux configurations and more widely impacts non-Linux platforms. Red Hat has released security advisories and updated packages to fix this issue, specifically providing patched rsync versions for Red Hat Enterprise Linux 6 Extended Lifecycle Support.
Potential Impact
Successful exploitation of this vulnerability can lead to use-after-free memory corruption, which may result in partial compromise of confidentiality, integrity, and availability of the affected system. The CVSS 3.1 base score is 7.4 (High), indicating significant risk if exploited. The impact includes potential unauthorized information disclosure, modification, or denial of service due to memory corruption.
Mitigation Recommendations
Red Hat has released security updates addressing this vulnerability, including patched rsync packages for Red Hat Enterprise Linux 6 Extended Lifecycle Support. Users should apply these official updates to remediate the issue. Since the vulnerability requires running rsync with the -X option, avoiding use of this option can reduce exposure but is not a complete mitigation. Patch status is confirmed by vendor advisories; therefore, applying the vendor-provided updates is the recommended remediation.
CVE-2026-41035: CWE-130 Improper Handling of Length Parameter Inconsistency in Samba rsync
Description
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.
CVSS v3.1
Score 7.4high
Affected software
pkg:github/rsyncproject/rsyncRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in rsync (versions 3.0.1 through 3.4.1) arises from improper handling of an untrusted length value during a qsort call in the receive_xattr function, leading to a use-after-free condition. Exploitation requires the victim to run rsync with the -X option to handle extended attributes. The vulnerability affects many Linux configurations and more widely impacts non-Linux platforms. Red Hat has released security advisories and updated packages to fix this issue, specifically providing patched rsync versions for Red Hat Enterprise Linux 6 Extended Lifecycle Support.
Potential Impact
Successful exploitation of this vulnerability can lead to use-after-free memory corruption, which may result in partial compromise of confidentiality, integrity, and availability of the affected system. The CVSS 3.1 base score is 7.4 (High), indicating significant risk if exploited. The impact includes potential unauthorized information disclosure, modification, or denial of service due to memory corruption.
Mitigation Recommendations
Red Hat has released security updates addressing this vulnerability, including patched rsync packages for Red Hat Enterprise Linux 6 Extended Lifecycle Support. Users should apply these official updates to remediate the issue. Since the vulnerability requires running rsync with the -X option, avoiding use of this option can reduce exposure but is not a complete mitigation. Patch status is confirmed by vendor advisories; therefore, applying the vendor-provided updates is the recommended remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-04-16T06:53:04.777Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-41035","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:25173","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:25172","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:26542","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:23233","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:25044","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:25181","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:23245","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:20696","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:19152","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:20601","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:20602","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:20604","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:20603","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:19368","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:17481","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:25170","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:25190","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:25149","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:29197","vendor":"Red Hat"}]
Threat ID: 69e08ce482d89c981f5edf33
Added to database: 04/16/2026, 07:16:52 UTC
Last enriched: 07/16/2026, 08:59:27 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 162
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.