Cyber Resilience

CVE-2026-41035

Samba Rsync 3.0.1 – 3.4.1

Public PoC
Published
16 April 2026
Modified
15 July 2026
CVSS Score v3.1 7.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
EPSS Score 0.0039 32th percentile
Risk Priority 53 floored blend · peak EPSS

Summary

CVE-2026-41035 is a high-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Samba Rsync. Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-41035 is a use-after-free vulnerability (CWE-130) in rsync versions 3.0.1 through 3.4.1, stemming from the receive_xattr function's reliance on an untrusted length value passed to a qsort call. The flaw affects rsync receivers when invoked with the -X (or --xattrs) option to handle extended attributes. On Linux systems, many but not all common configurations are vulnerable, while non-Linux platforms face broader exposure.

Exploitation is network-accessible (AV:N) with low attack complexity (AC:L), requiring low privileges (PR:L) and no user interaction (UI:N), resulting in a scope change (S:C) and low impacts to confidentiality, integrity, and availability (C:L/I:L/A:L), for an overall CVSS v3.1 score of 7.4. An attacker acting as a sender can trigger the issue against a victim receiver processing extended attributes, potentially leading to memory corruption.

Advisories and patches are detailed in Rsync GitHub issue #871 and the project's releases page, with additional discussions in oss-security mailing list posts from April 2026, including announcements on April 16 and 22.

EU & UK References

Vulnerability Data

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.…

more

Non-Linux platforms are more widely vulnerable.

CWE(s)
CWE-130CWE-805

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-45232Same product: Samba Rsync
CVE-2026-43618Same product: Samba Rsync
CVE-2026-43620Same product: Samba Rsync
CVE-2026-43617Same product: Samba Rsync
CVE-2026-43619Same product: Samba Rsync
CVE-2026-29518Same product: Samba Rsync
CVE-2023-5568Same vendor: Samba
CVE-2023-4154Same vendor: Samba
CVE-2025-20202Shared CWE-805
CVE-2026-0716Shared CWE-805

Affected Assets

samba
rsync
3.0.1 — 3.4.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.5
  • V4.2.1
  • V4.2.2
  • V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover length-parameter inconsistencies through targeted parsing tests.

SI-10 Information Input Validation good match

Input validation enforces correct length-to-data consistency checks on parsed messages before processing.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require explicit bounds checking and correct length calculations when performing buffer operations.

SI-16 Memory Protection partial match

Memory protection mechanisms limit the blast radius when an incorrect length value causes an out-of-bounds access.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce length validation and input sanitization during coding and review.

ID.RA-01 partial match
prevents

Vulnerability identification can discover buffer-length flaws but does not prevent their introduction.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect length-inconsistency vulnerabilities before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and length checks that directly address inconsistent length fields.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for handling message lengths and data structures.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require robust parsing and bounds checking to prevent length-related flaws.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.

References