# CVE-2026-41035: Use after free in rsync > An attacker can trigger a use-after-free in rsync when the receiver uses the -X flag, potentially leading to code execution or denial of service. - **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Apr 2026 - **Updated:** 4 Sep 2026 - **Also known as:** ALPINE-CVE-2026-41035, ALSA-2026:17481, ALSA-2026:19152, AZL-82958, BELL-CVE-2026-41035, CLSA-2026-1778940132, CLSA-2026-1779131668, CLSA-2026-1779154430, CLSA-2026-1780054763, CLSA-2026-1780054955, CLSA-2026-1780055137, CLSA-2026-1780062116, CLSA-2026-1780062671, CLSA-2026-1780064425, CLSA-2026-1780066764, CLSA-2026-1780388397, CLSA-2026-1780388593, CLSA-2026-1780389337, DEBIAN-CVE-2026-41035, ECHO-96cc-2c47-feab, GHSA-m34r-4v3r-pp9v, JLSEC-2026-627, MGASA-2026-0101, OESA-2026-2150, RHSA-2026:17481, RHSA-2026:19152, RHSA-2026:20601, RHSA-2026:25149, RHSA-2026:25170, RHSA-2026:25172, RHSA-2026:25173, RHSA-2026:25190, RLSA-2026:17481, RLSA-2026:19152, SUSE-SU-2026:2002-1, SUSE-SU-2026:21676-1, SUSE-SU-2026:21686-1, UBUNTU-CVE-2026-41035, openSUSE-SU-2026:10775-1 ## What is CVE-2026-41035? CVE-2026-41035 is a high-severity use after free vulnerability in Samba rsync, published on 16 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-805 (Buffer Access with Incorrect Length Value), CWE-130 (Improper Handling of Length Parameter Inconsistency) ## Which versions are affected by CVE-2026-41035? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `rsync` | AlmaLinux:10 | All versions | 3.4.1-6.el10_2 | | `rsync-daemon` | AlmaLinux:10 | All versions | 3.4.1-6.el10_2 | | `rsync-rrsync` | AlmaLinux:10 | All versions | 3.4.1-6.el10_2 | | `rsync` | AlmaLinux:8 | All versions | 3.1.3-25.el8_10 | | `rsync-daemon` | AlmaLinux:8 | All versions | 3.1.3-25.el8_10 | | `rsync` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.1-6.el10_2 | | `rsync-daemon` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.1-6.el10_2 | | `rsync-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.1-6.el10_2 | | `rsync-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.1-6.el10_2 | | `rsync-rrsync` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.1-6.el10_2 | | `rsync` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.1.3-25.el8_10 | | `rsync-daemon` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.1.3-25.el8_10 | | `rsync-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.1.3-25.el8_10 | | `rsync-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.1.3-25.el8_10 | | `rsync` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:3.1.3-12.el8_4.7 | | `rsync-daemon` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:3.1.3-12.el8_4.7 | | `rsync` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:3.1.3-14.el8_6.10 | | `rsync` | Red Hat:rhel_e4s:8.8::baseos | All versions | 0:3.1.3-20.el8_8.5 | | `rsync-daemon` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:3.2.3-9.el9_0.5 | | `rsync` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:3.2.3-9.el9_0.5 | | `rsync` | Red Hat:rhel_els:6 | All versions | 0:3.0.6-12.el6_10.3 | | `rsync` | Red Hat:rhel_els:7 | All versions | 0:3.1.2-12.el7_9.3 | | `rsync` | Red Hat:rhel_eus_long_life:8.4::baseos | All versions | 0:3.1.3-12.el8_4.7 | | `rsync-daemon` | Red Hat:rhel_eus_long_life:8.4::baseos | All versions | 0:3.1.3-12.el8_4.7 | | `rsync` | Red Hat:rhel_eus_long_life:8.6::baseos | All versions | 0:3.1.3-14.el8_6.10 | | `rsync` | Red Hat:rhel_tus:8.8::baseos | All versions | 0:3.1.3-20.el8_8.5 | | `rsync` | Rocky Linux:10 | All versions | 0:3.4.1-6.el10_2 | | `rsync` | Rocky Linux:8 | All versions | 0:3.1.3-25.el8_10 | | `rsync` | openSUSE:Tumbleweed | All versions | 3.4.1-5.1 | Products: Samba Rsync. ## How do I fix CVE-2026-41035? Upgrade to a fixed version. ## Is CVE-2026-41035 being exploited? There is no known exploitation of CVE-2026-41035 in the wild and no public exploit code. ## Other vulnerabilities in Samba rsync - [CVE-2017-15994](https://insights.sbomify.com/CVE-2017-15994/): Security feature bypass in n/a (critical 9.8) - [CVE-2026-53791](https://insights.sbomify.com/CVE-2026-53791/): rsync < 3.5.0 Daemon IP Spoofing via PROXY Protocol Header (critical 9.1) - [CVE-2026-70461](https://insights.sbomify.com/CVE-2026-70461/): rsync 3.2.5 < 3.5.0 Heap Out-of-Bounds Write via files-from Entry (high 8.8) - [CVE-2026-70455](https://insights.sbomify.com/CVE-2026-70455/): rsync 3.4.2 < 3.5.0 DoS via --zt Zstandard Compression Thread Exhaustion (high 8.7) - [CVE-2026-70463](https://insights.sbomify.com/CVE-2026-70463/): rsync 3.1.0 < 3.5.0 Authorization Bypass via auth users Directive Parsing (high 8.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-41035 and fix it if it is affected. What it is: CVE-2026-41035 is a high-severity use after free vulnerability in Samba rsync, published on 16 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-41035 in the wild and no public exploit code. Affected product: Samba rsync. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-41035/ (Markdown: https://insights.sbomify.com/CVE-2026-41035/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41035 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41035 - OSV: https://osv.dev/vulnerability/CVE-2026-41035 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-41035/ Summaries are generated and may contain mistakes; the official description above is the record.